-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editorial suggestions for consistent links to definitions and capitalization #3038
Changes from 71 commits
3da8ed1
579e8dc
427bdcb
3fae2d2
c569ace
eb8dd36
6642b57
2deb386
d7b66a6
46a5330
681fed3
c6aa5a1
4897997
44632ad
5d0396e
14a9fcf
5b9d388
51bb9bc
9a7287b
22c66c1
969bd8c
f06691f
4577ce1
50d3282
085b329
6a6c3af
4741929
e074871
cc0773c
cd467f3
85ef905
f3f645c
be25fca
4b2a7e4
70ce5f2
8556b6a
c063946
d266876
6e9d0d4
fb7d01e
b2af915
b716675
dc02557
6678982
02a4fba
307b91a
d0d3b39
f6aa1f0
cfeb046
1c61c8a
3a27a71
c02324f
2815923
ea4ba29
fedb967
760dcb5
655930f
60d8273
ec929db
d51622c
68d26c2
083f39a
18ff303
84267c2
9744fa5
9e69203
580eccc
2acec12
735ee3c
ea8ef6b
ac8a6fc
ad93d52
4efd0cf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I personally don't see any "win" by adding the link, but it doesn't seem to create a problem changing it either. |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It looks like there was no definition of "state" in 2.0; it's there in 2.1, but not marked as "New". @alastc I'm assuming that as long as this link exists in 2.1 and 2.2, we're okay, since we wouldn't be touching 2.0. |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This seems appropriate. All uses of "block of text" or "blocks of text" work when considering this as programmatic text. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
<dt><dfn id="dfn-blocks-of-text">blocks of text</dfn></dt> | ||
<dt><dfn id="dfn-blocks-of-text" data-lt="block of text">blocks of text</dfn></dt> | ||
<dd> | ||
|
||
<p>more than one sentence of text</p> | ||
<p>more than one sentence of <a>text</a></p> | ||
mbgower marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,7 @@ | ||
<dt><dfn id="dfn-programmatically-set">programmatically set</dfn></dt> | ||
<dd> | ||
|
||
<p>set by software using methods that are supported by user agents, including assistive | ||
technologies | ||
<p>set by software using methods that are supported by <a>user agents</a>, including <a>assistive technologies</a> | ||
</p> | ||
|
||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
<dt><dfn id="dfn-regions" data-lt="regions">region</dfn></dt> | ||
<dd> | ||
<p>perceivable, programmatically determined section of content</p> | ||
<p>perceivable, <a>programmatically determined</a> <a>section</a> of content</p> | ||
<p class="note">In HTML, any area designated with a landmark role would be a region.</p> | ||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
<dt><dfn id="dfn-single-pointer">single pointer</dfn></dt> | ||
<dd> | ||
<p>an input that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus.</p> | ||
<p class="note">In contrast to single pointer inputs, multipoint interactions involve the use of two or more pointers at the same time – such as two finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.</p> | ||
<p>a <a>pointer input</a> that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus.</p> | ||
<p class="note">In contrast to single pointer inputs, multipoint interactions involve the use of two or more pointers at the same time – such as two finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.</p> | ||
</dd> | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
<dt><dfn id="dfn-states" data-lt="states">state</dfn></dt> | ||
<dd> | ||
|
||
<p>dynamic property expressing characteristics of a user interface component that may change in response to user action or automated processes</p> | ||
<p>dynamic property expressing characteristics of a <a>user interface component</a> that may change in response to user action or automated processes</p> | ||
<p>States do not affect the nature of the component, but represent data associated with the component or user interaction possibilities. Examples include focus, hover, select, press, check, visited/unvisited, and expand/collapse.</p> | ||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
<dt><dfn id="dfn-status-messages" data-lt="status messages">status message</dfn></dt> | ||
<dd> | ||
|
||
<p>change in content that is not a <a>change of context</a>, and that provides information to the user on the success or results of an action, on the waiting state of an application, on the progress of a process, or on the existence of errors</p> | ||
<p>change in content that is not a <a>change of context</a>, and that provides information to the user on the success or results of an action, on the waiting state of an application, on the progress of a <a>process</a>, or on the existence of errors</p> | ||
|
||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
<dt><dfn id="dfn-targets" data-lt="targets">target</dfn></dt> | ||
<dd> | ||
|
||
<p>region of the display that will accept a pointer action, such as the interactive area of a user interface component</p> | ||
<p>region of the display that will accept a pointer action, such as the interactive area of a <a>user interface component</a></p> | ||
<p class="note">If two or more targets are overlapping, the overlapping area should not be included in the measurement of the target size, except when the overlapping targets perform the same action or open the same page.</p> | ||
|
||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
<dt><dfn id="dfn-user-inactivity">user inactivity</dfn></dt> | ||
<dd> | ||
<p>any continuous period of time where no user actions occur</p> | ||
<p>The method of tracking will be determined by the web site or application.</p> | ||
<p>The method of tracking will be determined by the website or application.</p> | ||
</dd> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
<dt class="new"><dfn id="dfn-bounding-boxes" data-lt="bounding boxes|bounding box">minimum bounding box</dfn></dt> | ||
<dd class="new"> | ||
<p class="change">New</p> | ||
<p>the smallest enclosing rectangle aligned to the horizontal axis within which all the points of a shape lie. For components which wrap onto multiple lines as part of a sentence or block of text (such as hypertext links), the bounding box is based on how the component would appear on a single line.</p> | ||
<p>the smallest enclosing rectangle aligned to the horizontal axis within which all the points of a shape lie. For components which wrap onto multiple lines as part of a sentence or <a>block of text</a> (such as hypertext links), the bounding box is based on how the component would appear on a single line.</p> | ||
mbgower marked this conversation as resolved.
Show resolved
Hide resolved
|
||
</dd> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Focus indicator is a definition added in WCAG 2.2. So in 2.2 a link to "focus indicator" can exist, but the 2.1 (and 2.0) version of the same file cannot have that link since the definition doesn't exist. @kfranqueiro and @alastc can our model now support this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as this is only happening within the
guidelines
folder I think we're okay; the plan for building 2.1 is to use a snapshot of the 2.1 TR so it won't be looking at that folder in the main branch (which contains 2.2-specific things).If you discover anything like this directly within the source of Understanding pages, that would definitely be worth flagging because we would need to conditionalize it somehow. (Currently the only conditionalization I'm aware of in that regard is for the "New in WCAG 2.2" callouts.)