During the redesign/re-architecture of the accessibility site, the content on a lot of pages was updated and some useful content was removed because it didn't quite fit with the more focused topic of the updated pages. It's still good content and we should consider if new guides or pages should be created in future with these topics in mind.
Some of the content that was removed was:
Removed from the manual testing page:
High contrast
It is also useful to test sites with Custom CSS stylesheets & Windows High Contrast Mode to determine if there are any elements which are obscured.
- Site works in Windows High Contrast Mode.
Dark mode
Many browsers are now coming out with dark mode and reader mode options. These can be useful for a range of people with disabilities, but also for people looking to optimize their time online. Pages need to be set up properly to access this.
- Dark mode works effectively, even when forced by a browser extension.
Reader mode
Mobile testing
- Interactions work with touch interaction (smartphone/tablet).
Removed from the screen reader testing page (this used to be a more general AT page):
AT software:
There are a range of other assistive technologies which are available to support other disabilities. We often overlook voice control, with tools like Dragon Naturally Speaking, Windows Speech and Apple's Voice Control. There is a range of disabilities where motion for the user is severely limited and where simple switches need to be employed to navigate the website. Probably the most famous switch user was Stephen Hawking used a handheld switch early in his life, but then moved to a cheek switch when he lost control of his hands.
Whatever software you choose, it is always good practice to support the latest two major releases of assistive technology to allow for late adopters, and to test with actual blind users. It takes considerable effort for a sighted user to learn to use a screen reader how a blind user does., and simply being able to use one of these assistive technology tools may not be the best way to evaluate if a page is accessible.
Does your team have the deep knowledge that is required to understand how a blind user actually understands the page?
Is user testing done with people who are completely blind, partially sighted, and who become blind as adults? Screen reader users have a lot of flexibility.
During the redesign/re-architecture of the accessibility site, the content on a lot of pages was updated and some useful content was removed because it didn't quite fit with the more focused topic of the updated pages. It's still good content and we should consider if new guides or pages should be created in future with these topics in mind.
Some of the content that was removed was:
Removed from the manual testing page:
High contrast
It is also useful to test sites with Custom CSS stylesheets & Windows High Contrast Mode to determine if there are any elements which are obscured.
Dark mode
Many browsers are now coming out with dark mode and reader mode options. These can be useful for a range of people with disabilities, but also for people looking to optimize their time online. Pages need to be set up properly to access this.
Reader mode
Mobile testing
Removed from the screen reader testing page (this used to be a more general AT page):
AT software:
There are a range of other assistive technologies which are available to support other disabilities. We often overlook voice control, with tools like Dragon Naturally Speaking, Windows Speech and Apple's Voice Control. There is a range of disabilities where motion for the user is severely limited and where simple switches need to be employed to navigate the website. Probably the most famous switch user was Stephen Hawking used a handheld switch early in his life, but then moved to a cheek switch when he lost control of his hands.
Whatever software you choose, it is always good practice to support the latest two major releases of assistive technology to allow for late adopters, and to test with actual blind users. It takes considerable effort for a sighted user to learn to use a screen reader how a blind user does., and simply being able to use one of these assistive technology tools may not be the best way to evaluate if a page is accessible.
Does your team have the deep knowledge that is required to understand how a blind user actually understands the page?
Is user testing done with people who are completely blind, partially sighted, and who become blind as adults? Screen reader users have a lot of flexibility.