[BCAB] Whether it is Accessible or Useable that is the Question

Barry Hill barry.hill3 at sky.com
Thu Oct 10 14:16:25 BST 2019

For me, accessibility and usability are semantics.  I go by the POUR model:
A website or app needs to be Perceivable, Operable, Understandable, and
Robust.  Here's more on that:

, ,


-----Original Message-----
From: Vic Pereira <vic.pereira at virn.ca> 
Sent: Wednesday, October 9, 2019 9:27 PM
To: 'BCAB Discussion List' <bcab at lists.bcab.org.uk>
Subject: [BCAB] Whether it is Accessible or Useable that is the Question

Good day everyone

Determining whether or not a website is accessible or useable has always
been a difficult question for me. Several years ago I helped a bit with the
WCAG effort. At times it was obvious when a website wasn't accessible to a
person who had low vision or no vision, especially when adaptive or
assistive technologies needed to be used.

I also came across several examples of websites that were more difficult,
however with some investment in learning the basic text to speech software
navigation functions the experience became much more positive.

When a website uses embedded headings, tables, actual controls etc. it can
work very nicely if a person is comfortable using the text to speech
software functions to move between elements and navigate tables.

Now if a person wasn't able to invest the time in learning the adaptive or
assistive technology and issues complaints about websites not being useable
I have no idea where to put the blame. This is outside of having a learning
or cognitive disability of course.


To find out more about BCAB and the benefits that membership can bring,
please visit our website: https://www.bcab.org.uk/ Manage your subscription
by logging in with your BCAB account details at :
Access the publicly searchable list archives at:
To discuss matters relating to the mailing list, please email:
moderator at bcab.org.uk.

More information about the Bcab mailing list