IAAP WEB ACCESSIBILITY SPECIALIST (WAS) UPDATED
QUESTIONS AND ANSWERS
Perceivable - CORRECT ANSWER✅✅✅Information and user interface components must be
presentable to users in ways persons with disabilities can perceive (including blindness, low vision,
deafness and hearing loss, limited movements and cognitive limitations).
Operable - CORRECT ANSWER✅✅✅User interface components and navigation must be operable
(functionality from keyboard)
Robust - CORRECT ANSWER✅✅✅Content must be robust enough that it can be interpreted reliably
by a wide variety of user agents, including assistive technologies
WAI-ARIA - CORRECT ANSWER✅✅✅Web Accessibility Initiative Accessible Rich Internet Applications
Created to increase the accessibility of content - dynamic content in particular - for assistive technology
users.
WAI-ARIA defines attributes that can be added to standard HTML to define the name, role and values
(properties and states) of elements - especially custom widgets
One of the goals of WAI-ARIA is to make web applications behave more like software components.
WAI-ARIA widgets interact with the accessibility API of the operating system, providing assistive
technologies with the semantics and live updates necessary for full accessibility.
ARIA enables developers to mark up dynamic content, including custom controls created with AJAX,
HTML and JavaScript to improve their accessibility
ATAG - CORRECT ANSWER✅✅✅Authoring Tool Accessibility Guidelines
, The ATAG specification requires authoring tools (HTML/web editors, content management systems,
social media sites, blog commenting features, discussion forums, user rating features etc) to:
1) Have an accessible user interface
2)Support the production of accessible content
Normative documents - CORRECT ANSWER✅✅✅define accessibility practices required for
conformance (to a specification)
Non-normative documents - CORRECT ANSWER✅✅✅provide guidance and techniques for
interpreting and conforming with the normative requirements, but non-normative techniques are not
required for conformance.
Non-normative documents provide information about the different way web technologies need to work
with authoring tools, user agents and assistive technologies
Non-normative documents may change more frequently than normative documents, to adapt to
changing technologies and current best practices
ARIA Label - CORRECT ANSWER✅✅✅The attribute that maps to the Accessible Name which is
handed to the screen reader. The ARIA labelling attributes override HTML accessible names, so only use
them when you can't use the generic HTML labels.
To provide supplementary information use aria-describedby which is presented to the screen reader
separately from the accessible name and doesn't override it
aria-label (property) - CORRECT ANSWER✅✅✅Defines a string value that labels the current
element. The purpose of aria-label is the same as that of aria-labelledby. It provides the user with a
recognizable name of the object.
If the label text is visible on screen on screen, authors should use aria-labelledby
QUESTIONS AND ANSWERS
Perceivable - CORRECT ANSWER✅✅✅Information and user interface components must be
presentable to users in ways persons with disabilities can perceive (including blindness, low vision,
deafness and hearing loss, limited movements and cognitive limitations).
Operable - CORRECT ANSWER✅✅✅User interface components and navigation must be operable
(functionality from keyboard)
Robust - CORRECT ANSWER✅✅✅Content must be robust enough that it can be interpreted reliably
by a wide variety of user agents, including assistive technologies
WAI-ARIA - CORRECT ANSWER✅✅✅Web Accessibility Initiative Accessible Rich Internet Applications
Created to increase the accessibility of content - dynamic content in particular - for assistive technology
users.
WAI-ARIA defines attributes that can be added to standard HTML to define the name, role and values
(properties and states) of elements - especially custom widgets
One of the goals of WAI-ARIA is to make web applications behave more like software components.
WAI-ARIA widgets interact with the accessibility API of the operating system, providing assistive
technologies with the semantics and live updates necessary for full accessibility.
ARIA enables developers to mark up dynamic content, including custom controls created with AJAX,
HTML and JavaScript to improve their accessibility
ATAG - CORRECT ANSWER✅✅✅Authoring Tool Accessibility Guidelines
, The ATAG specification requires authoring tools (HTML/web editors, content management systems,
social media sites, blog commenting features, discussion forums, user rating features etc) to:
1) Have an accessible user interface
2)Support the production of accessible content
Normative documents - CORRECT ANSWER✅✅✅define accessibility practices required for
conformance (to a specification)
Non-normative documents - CORRECT ANSWER✅✅✅provide guidance and techniques for
interpreting and conforming with the normative requirements, but non-normative techniques are not
required for conformance.
Non-normative documents provide information about the different way web technologies need to work
with authoring tools, user agents and assistive technologies
Non-normative documents may change more frequently than normative documents, to adapt to
changing technologies and current best practices
ARIA Label - CORRECT ANSWER✅✅✅The attribute that maps to the Accessible Name which is
handed to the screen reader. The ARIA labelling attributes override HTML accessible names, so only use
them when you can't use the generic HTML labels.
To provide supplementary information use aria-describedby which is presented to the screen reader
separately from the accessible name and doesn't override it
aria-label (property) - CORRECT ANSWER✅✅✅Defines a string value that labels the current
element. The purpose of aria-label is the same as that of aria-labelledby. It provides the user with a
recognizable name of the object.
If the label text is visible on screen on screen, authors should use aria-labelledby
