My name's Simon Borer and I am a Toronto-based web developer and educator specializing in accessibility.
Read about my work in my CV, or get in touch.
People should be able to use websites and public services without running into barriers. Accessibility is an equity issue, and it's central to how I approach development.
The Web Content Accessibility Guidelines (WCAG) provide testable requirements for making web content more accessible to people with disabilities. I use those requirements alongside practical testing to guide my work.
For me, that means clear content, semantic HTML, keyboard access, and careful testing with assistive technology. It also means helping developers, designers, and content teams understand the barriers they're working to remove.
I develop accessible websites for Ontario's Ministry of Labour, Immigration, Training and Skills Development. Since joining in March 2023, I've combined hands-on development with accessibility testing, code review, and helping other developers work through accessibility problems.
I've worked in web development since 2012. I started, like so many of us, by hacking my band's MySpace theme.
I followed some of my bandmates into Humber's Web Development program, and went on to work for a variety of ad agencies. I worked on campaigns for major brands like McDonald's and Chevrolet (and coded HTML emails for George Michael - yes, the George Michael).
My specialization in accessibility began while working with the Bank of Montreal, where, during my four years there as a Senior Software Developer, I became the accessibility Subject Matter Expert. From 2018 to 2023, I designed and taught Accessibility & Usability in Humber College's postgraduate Web Development program.
I've been a fan of the internet since 1993, when I made my first post on an X-Files BBS. Despite Mulder & Scully's multiple - link opens in a new tab negative experiences - link opens in a new tab, I believe in the principles of the open web - link opens in a new tab, as interoperability is the foundation of accessibility.
What do ARIA attributes add to HTML's native semantics? This introduction explains the vocabulary and how it helps describe an interface to assistive technology. A starting point for understanding roles, states, and properties. Read the ARIA introduction
Emojis can communicate more than you intended when read aloud. Explore ways to use them thoughtfully, with screen-reader users in mind 🏆. Read about accessible emojis
I designed and taught this postgraduate course from 2018 to 2023. The notes connect practical accessibility with usability study planning, testing, analysis, and recommendations. They include assignments and demonstrations for students to work through. These are historical teaching materials; some technical details may now be out of date. Explore the course materials
Accessibility isn't just for developers. The words, images, and structure of a page matter too. This guide looks at the content team's part in making information easier to find, understand, and use. Read the accessible content guide
There are lots of options in front-end code for controlling visibility, including native attributes, CSS property values, and helper classes from popular front-end libraries like Bootstrap, Foundation and HTML Boilerplate. It can be tough to remember which option shows or hides things for whom. Here’s a little cheat sheet and demo to help! Read more about visibility...
Accessibility is one of those things that is never ‘done’. It’s a principle. If accessibility (digital or otherwise) is something you want to know more about, let’s take a moment to look at where to start.Read more about where to start...
WebAIM (Web Accessibility in Mind) is a non-profit run out of Utah State University's Center for Persons with Disabilities, and is one of the most respected resources for Web Accessibility. Check out their 'Intro' to get started.
MDN Web Docs is, for my money, one of the most useful development references on the web. Its accessibility docs are no exception.
The W3C's Web Content Accessibility Guidelines overview explains the standards and links to WCAG 2.2, supporting guidance, and a quick reference. It's a useful starting point for understanding the requirements.
Chrome's Lighthouse auditing tool not only lets you check accessibility concerns through dev tools, but can also run as a CLI or Node module, meaning you can make it a part of your linting and build process.
WebAIM's WAVE tool lets you check a page either through their site or using one of their browser extensions.
The W3C's ARIA Authoring Practices Guide explains accessible interaction patterns, keyboard behaviour, and the roles, states, and properties used in common widgets.