Skip to content

Commit e041c1c

Browse files
fstrrpatrickhlaukealastcmbgowerWilcoFiers
authored
Update references in non-normative docs (#3854)
- Replace reference to focus section of HTML 4.01 spec with reference to focus section of the HTML living standard in non-normative documents - correct uses of lists to be either unordered or ordered as appropriate - correct relative links --------- Co-authored-by: Patrick H. Lauke Co-authored-by: Alastair Campbell Co-authored-by: Mike Gower Co-authored-by: Wilco Fiers Co-authored-by: Mike Gower Co-authored-by: Giacomo Petri Co-authored-by: Bruce Bailey
1 parent 9139768 commit e041c1c

File tree

1 file changed

+23
-73
lines changed

1 file changed

+23
-73
lines changed

understanding/20/focus-order.html

Lines changed: 23 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,6 @@

In brief

2121
<section id="intent">
2222
<h2>Intent of Focus Orderh2>
2323

24-
2524
<p>The intent of this Success Criterion is to ensure that when users navigate sequentially
2625
through content, they encounter information in an order that is consistent with the
2726
meaning of the content and can be operated from the keyboard. This reduces confusion
@@ -34,10 +33,9 @@

Intent of Focus Order

3433
<p>The way that sequential navigation order is determined in Web content is defined by
3534
the technology of the content. For example, simple HTML defines sequential navigation
3635
via the notion of tabbing order. Dynamic HTML may modify the navigation sequence using
37-
scripting along with the addition of a tabindex attribute to allow focus to additional
38-
elements. If no scripting or tabindex attributes are used, the navigation order is
39-
the order that components appear in the content stream. (See HTML 4.01 Specification,
40-
section 17.11, "Giving focus to an element").
36+
scripting along with the addition of a <code class="language-html">tabindexcode> attribute to allow focus to additional
37+
elements. If no scripting or <code class="language-html">tabindexcode> attributes are used, the navigation order is
38+
the order that components appear in the content stream. (See <a href="https://html.spec.whatwg.org/multipage/interaction.html#focus"><cite>Focuscite> in the HTML Living Standarda>).
4139
p>
4240

4341
<p>An example of keyboard navigation that is not the sequential navigation addressed
@@ -50,7 +48,7 @@

Intent of Focus Order

5048
p>
5149

5250
<p>The focus order may not be identical to the programmatically determined reading order
53-
(see Success Criterion 1.3.2) as long as the user can still understand and operate
51+
(see <a href="meaningful-sequence.html">Success Criterion 1.3.2a>) as long as the user can still understand and operate
5452
the Web page. Since there may be several possible logical reading orders for the content,
5553
the focus order may match any of them. However, when the order of a particular presentation
5654
differs from the programmatically determined reading order, users of one of these
@@ -145,7 +143,7 @@

Examples of Focus Order

145143
<p>An HTML Web page is created with the left hand navigation occurring in the HTML after
146144
the main body content, and styled with CSS to appear on the left hand side of the
147145
page. This is done to allow focus to move to the main body content first without requiring
148-
tabIndex attributes or JavaScript.
146+
<code class="language-html">tabindexcode> attributes or JavaScript.
149147
p>
150148

151149
<div class="note">
@@ -186,110 +184,62 @@

Resources for Focus Order

186184
<section id="techniques">
187185
<h2>Techniques for Focus Orderh2>
188186

189-
190187
<section id="sufficient">
191188
<h3>Sufficient Techniques for Focus Orderh3>
192189

193-
194190
<ul>
195-
196-
<li>
197-
198-
<a href="../Techniques/general/G59" class="general">Placing the interactive elements in an order that follows sequences and relationships
199-
within the content
200-
a>
201-
191+
<li>
192+
<a href="../Techniques/general/G59">Placing the interactive elements in an order that follows sequences and relationships within the contenta>
202193
li>
203-
204194
<li>
205-
206-
<p>Giving focus to elements in an order that follows sequences and relationships within
207-
the content using one of the following techniques:
195+
<p>Giving focus to elements in an order that follows sequences and relationships within the content using one of the following techniques:
208196
p>
209-
210197
<ul>
211-
212-
<li>
213-
214-
<a href="../Techniques/css/C27" class="css">Making the DOM order match the visual ordera>
215-
198+
<li>
199+
<a href="../Techniques/css/C27">Making the DOM order match the visual ordera>
216200
li>
217-
218201
<li>
219-
220-
<a href="../Techniques/pdf/PDF3" class="pdf">a>
221-
202+
<a href="../Techniques/pdf/PDF3">a>
222203
li>
223-
224204
ul>
225-
226205
li>
227-
228206
<li>
229-
230207
<p>Changing a Web page dynamically using one of the following techniques:p>
231-
232208
<ul>
233-
234-
<li>
235-
236-
<a href="../Techniques/client-side-script/SCR26" class="script">Inserting dynamic content into the Document Object Model immediately following its
237-
trigger element
209+
<li>
210+
<a href="../Techniques/client-side-script/SCR26">Inserting dynamic content into the Document Object Model immediately following its trigger element
238211
a>
239-
240212
li>
241-
242-
<li>
243-
244-
<a href="../Techniques/HTML/H102" class="script">Creating modal dialogs with the HTML dialog elementa>
245-
213+
<li>
214+
<a href="../Techniques/HTML/H102" class="script">Creating modal dialogs with the HTML dialog elementa>
246215
li>
247-
248-
<li>
249-
250-
<a href="../Techniques/client-side-script/SCR27" class="script">Reordering page sections using the Document Object Modela>
251-
216+
<li>
217+
<a href="../Techniques/client-side-script/SCR27" class="script">Reordering page sections using the Document Object Modela>
252218
li>
253-
254219
ul>
255-
256220
li>
257-
258-
ul>
259-
221+
ul>
260222
section>
261223

262224
<section id="advisory">
263225
<h3>Additional Techniques (Advisory) for Focus Orderh3>
264-
265226
section>
266227

267228
<section id="failure">
268229
<h3>Failures for Focus Orderh3>
269230

270-
271231
<ul>
272-
273-
<li>
274-
275-
<a href="../Techniques/failures/F44" class="failure">Failure of 2.4.3 due to using tabindex to create a tab order that does not preserve
276-
meaning and operability
232+
<li>
233+
<a href="../Techniques/failures/F44" class="failure">Failure of 2.4.3 due to using <code class="language-html">tabindexcode> to create a tab order that does not preserve meaning and operability
277234
a>
278-
279235
li>
280-
281-
<li>
282-
283-
<a href="../Techniques/failures/F85" class="failure">Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent
284-
to their trigger control in the sequential navigation order
285-
a>
286-
236+
<li>
237+
<a href="../Techniques/failures/F85" class="failure">Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
238+
a>
287239
li>
288-
289240
ul>
290241

291242
section>
292-
293243
section>
294244

295245
body>

0 commit comments

Comments
 (0)