Re: Groups.io accessibility enhancements.


Brian's Mail list account <bglists@...>
 

Thanks for this, am having issues with the uk nhs registration and survey sites as wee speak though the term thick comes to mind when discussing their reaction thus far.. grin.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Brian Vogel" <britechguy@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, January 04, 2019 2:28 PM
Subject: Re: [nvda] Groups.io accessibility enhancements.


Robert,

Good for you for doing the grunt work of communicating with Mark about accessibility issues. He tends to be quite responsive when he can be. What follows is something I recently sent a client who was facing the same sort of issues with a corporate website. It should also be useful here.

I wanted to make sure to send you what follows. It is not that you will necessarily use any of it directly, but these are powerful pieces of information to pass along when you're working with any organization where the goal is increasing the accessibility of their webpages.

The first is the WAVE Web Accessibility Evaluation Tool:

http://wave.webaim.org/
On this webpage you supply the web address of the webpage you wish to have analyzed from an accessibility perspective. The tool identifies all (or at least most) of the page coding errors that restrict accessibility and gives direct instructions on how to fix them. It can be invaluable information for web developers who have never taken accessibility into account and in showing them easy ways to do so going forward.

There is also a form and checklist at the webaim.org ( http://webaim.org/ ) site that can help web programmers:

https://webaim.org/techniques/ forms/ ( https://webaim.org/techniques/forms/ )
https://webaim.org/standards/ wcag/checklist ( https://webaim.org/standards/wcag/checklist )

The formal conventions document (or one of the major ones, there are a couple of others, and it makes reference to them) is the Web Content Accessibility Guidelines which are available here:

https://www.w3.org/TR/WCAG21/

These are all things you might want to pass along not only to tech geeks, but to those who are working with them to create new web content. Even the non-technically minded can find it enlightening to run WAVE against a webpage that's really accessible to a screen reader user then do the same for one that's not.
--

Brian *-* Windows 10 Home, 64-Bit, Version 1809, Build 17763

*A great deal of intelligence can be invested in ignorance when the need for illusion is deep.*

~ Saul Bellow, To Jerusalem and Back

Join nvda@nvda.groups.io to automatically receive all group messages.