HTML5 Accessibility

Accessibility
&Forms
in HTML5

Aaron Gustafson
Easy Designs, LLC
slideshare.net/AaronGustafson

Accessibility & Forms

2


ARIA maps the OS to the web


Semantics+


Landmarks
help users
navigate
quickly

All the site’s a play...
The role attribute
Defines the part an element is playing (assuming it’s different than the
semantics would otherwise imply).

<section id="main" role="main">

</section>


Landmark roles
application
A region of the page representing a unique software unit executing a set of tasks for its
users. It is an area where assistive technologies should also return browse navigation
keys back over to the web application in this region.
banner
A region that contains the prime heading or internal title of a page.
complementary
A supporting section of the document that remains meaningful even when separated
from the main content.
contentinfo
Metadata that applies to the parent document.
form
A region of the document that represents a collection of form-associated elements.
main
navigation
search


Landmark roles
main
The main content of a document.
navigation
A collection of navigational elements (usually links) for navigating the document or
related documents.
search
The search tool of a web document.


Structural roles
article
columnheader
definition
directory
document
group
heading
img
list
listitem
math
note
presentation
region
row
rowheader
separator


Structural roles
article
A section of a page that forms an independent part of a document, page, or site.
group
A set of user interface objects which are not intended to be included in a page summary
or table of contents by assistive technologies.
note
A section whose content is parenthetic or ancillary to the main content of the resource.
presentation
An element whose implicit native semantics will not be mapped to the accessibility API.
region
A large perceivable section of a web page or document, that the author feels is
important enough to be included in a page summary or table of contents.
separator
A divider that separates and distinguishes sections of content or groups of menu items.


Semantic comparison
Ad-hoc ARIA Role HTML5

#header, #top banner header (kind of)

#main, #content main none

#extra, .sidebar complementary, note aside

#footer, #bottom contentinfo footer

#nav navigation nav

.hentry article article


What is this!?


Widget roles
<span role="button">OK</span>


Widget roles

(of course <button>OK</button> would be better)


Widget roles


<div role="alert">
<p>Something went wrong.</p>
</div>


Widget roles


<div role="alert">
</div>

<div role="alertdialog">
<img src="x.png" alt="dismiss" role="button" />
</div>


Widget roles
alert marquee slider
alertdialog menuitem spinbutton
button menuitemcheckbox status
checkbox menuitemradio tab
combobox option tabpanel
dialog progressbar textbox
gridcell radio timer
link radiogroup tooltip
log scrollbar treeitem

Widget Container Roles
grid menubar tree
listbox tablist treegrid
menu toolbar


Widget properties
aria-activedescendant aria-multiline
aria-atomic aria-multiselectable
aria-autocomplete aria-orientation
aria-controls aria-owns
aria-describedby aria-posinset
aria-dropeffect aria-readonly
aria-flowto aria-relevant
aria-haspopup aria-required
aria-label aria-setsize
aria-labelledby aria-sort
aria-level aria-valuemax
aria-live aria-valuemin


What’s going on!?


Widget states
B B
(off) (on)

<span>
<img src="bold-off.png" alt="bold" />
</span>
<span>
<img src="bold-on.png" alt="bold" />
</span>


Widget states
B B
(off) (on)

<span>
<img src="bold-off.png" alt="not bold" />
</span>
<span>
</span>


Widget states
B B
(off) (on)

<span role="button" aria-pressed="false">
<img src="bold-off.png" alt="not bold" />
</span>
<span role="button" aria-pressed="true">
</span>


Widget states
aria-busy
aria-checked
aria-disabled
aria-expanded
aria-grabbed
aria-hidden
aria-invalid
aria-pressed
aria-selected
aria-valuenow (the W3C defines this as a “property”)
aria-valuetext (ditto)


Highlighting living content


Live regions


Live regions

<input class="tweet-counter" value="140" disabled="disabled">


Live regions

<span id="chars_left_notice" class="numeric">
<strong id="status-field-char-counter"
class="char-counter">140</strong>
</span>


Live regions

<span class="tweet-counter">140
<b class="hidden"> characters remaining</b></span>

.hidden {
position: absolute;
left: −999em;
}


Live regions

<span class="tweet-counter">maximum of 140 characters</span>

<span class="tweet-counter">140
<b class="hidden"> characters remaining</b></span>


Live regions

<span aria-live="polite" aria-atomic="true"
class="tweet-counter">140<b class="hidden">
characters remaining</b></span>


Notification options
off
change not announced

polite
change announced after user completes her current activity

assertive
user agent should interrupt the user’s activity, but not immediately


Who is Supporting WAI-ARIA?


For more
WAI-ARIA Spec
w3.org/TR/wai-aria/

WAI-ARIA Support in Browsers
paciellogroup.com/blog/aria-tests/ARIA-SafariaOperaIEFF.html


Fixing “broken” tables

HTML4 best practice
<table summary="Characteristics are given in the second column, with the negative
side in the left column and the positive side in the right column">
<caption>Characteristics with positive and negative sides</caption>
<thead>
<tr>
<th scope="col">Negative</th>
<th scope="col">Characteristic</th>
<th scope="col">Positive</th>
</tr>
</thead>
<tbody>
<tr>
<td>Sad</td>
<th scope="row">Mood</th>
<td>Happy</td>
</tr>

</tbody>
</table>

HTML5 options
<p>In the following table, characteristics are given in the second
column, with the negative side in the left column and the positive
side in the right column.</p>
<table>
<caption>Characteristics with positive and negative sides</caption>
<thead>
<tr>
</tr>
</thead>
<tbody>

</tbody>
</table>

HTML5 options
<table>
<caption>
<strong>Characteristics with positive and negative sides.</strong>
<p>Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.</p>
</caption>
<thead>
<tr>
</tr>
</thead>
<tbody>

</tbody>
</table>

HTML5 options
<table>
<caption>
<strong>Characteristics with positive and negative sides.</strong>
<details>
<summary>Help</summary>
column.</p>
</details>
</caption>
<thead>
<tr>
</tr>
</thead>
<tbody>

</tbody>
</table>

HTML5 options
<figure>
<figcaption>Characteristics with positive and negative sides</figcaption>
column.</p>
<table>
<thead>
<tr>
</tr>
</thead>
<tbody>

</tbody>
</table>
</figure>

HTML5 options
<table>
<thead>
<tr>
</tr>
</thead>
<tbody>
<tr>
<th scope="row">Mood</th>
<td>Sad</td>
<td>Happy</td>
</tr>

</tbody>
</table>


More usable forms


Dates and times
<input type=”datetime”>
A UI control for selecting a date and time that includes timezone information.

<input type=”datetime-local”>
A UI control for selecting a date and time that does not include timezone information.

<input type=”date”>
A UI control for selecting a date with access to all date components
(day, month and year).

<input type=” month”>
A UI control for selecting a date that provides access to month and year only.

<input type=”time”>
A UI control for selecting a time that does not include timezone information.

<input type=”week”>
A UI control for selecting a date that provides access to week and year only.


Dates and times

Safari

Opera

<input type="date" name="dob"/>


Numbers
<input type=”number”>
A UI control for selecting a number.

<input type=”range”>
A UI control for selecting an imprecise number.


Numbers

<input type="number" name="foo"/>

<input type="range" min="1" max="11" name="foo"/>


New types
<input type=”email”>
A UI control for entering an email.

<input type=”url”>
A UI control for entering a URL.

<input type=”tel”>
A UI control for entering a telephone number.


New types

<input type="email" …/> <input type="url" …/>


New types
<input type=”search”>
A UI control for plain text editing of one or more search terms.

my search terms x


New types
<input type=”color”>
A UI control for selecting a color.

#EC4D0E


UI control attributes
autocomplete
Tells the User Agent whether or not the value should be stored.

autofocus
Tells the User Agent to bring focus to the form control on page load.

form
An id reference to the form to which a given control belongs.

required
Indicated the form control must be provided a value.

placeholder
Offers users a short hint about the required value.


Value control
min and max
Lower and upper boundary for an element value (dates, time, and numbers only).

step
The granularity of values allowed (dates, time, and numbers only).

<input type="range" min="1" max="11" step="0.5" .../>


Value control
pattern
A regular expression pattern that the User Agent should validate the input against.

<input type="text"
pattern="d{6}w{3}"
placeholder="6 digits followed by 3 letters"
.../>

Value control
pattern
An id reference to a datalist element containing acceptable values.

<input type="text" list="countries" name="country"/>
<datalist id="countries">
<option>Afghanistan</option>
<option>Åland Islands</option>

</datalist>


Slides available at
http://slideshare.net/AaronGustafson

This presentation is licensed under
Creative Commons
Attribution-Noncommercial-Share Alike 3.0

ﬂickr Photo Credits
“HTML5 logo in Braille” by Ted Drake
“Dual Samsung Monitors” by steve-uk
“Statue of Liberty” by gadl
“Lego” by DavePress
“iFlickr touch screen” by exfordy
“Green Plant” by kevin1024

HTML5 Accessibility

More Related Content

Similar to HTML5 Accessibility (20)

More from Aaron Gustafson (20)

HTML5 Accessibility