My process

Keyboard navigation

Testing with keyboard checking, users using assisted technology can navigate the screen. 

Reviewing content

Making sure content is understandable and explicit and appropriately applying practices such as using hidden text and alt text.

Assistive Technology

Putting myself in the users shoes and testing with assistive tech such as screen readers, screen magnification and speech recognition on a range of devices. To spot potential issues with interactions.

Colour contrast Checking

Checking colour contrast between text and background of content to ensure users can perceive the information. 

Semantic structure

Ensuring the use of the correct html elements to structure a page and not using elements that are semantically meaningless such as a <div>. Appropriate use of headings so users don’t skip over important bits of content.

Responsiveness and mobile design

I strongly believe this plays a huge role in content accessibility. Users with low vision need to resize text without adding horizontal scrolling to a page. Fixed, non-fluid sizes cause overlapping or cutoff text when a web page’s text is resized. Similarly, tables and non-fluid pages used to lay out content cause reading order issues for users of screen readers. One size fits all sites do not fit the needs of users with disabilities. Responsive design principles, including fluid layouts, benefit users with disabilities on desktops as well as on mobile devices.