Editorial pass by Bruce for use of "requires" #328
Conversation
- Added year and Revised Standards to 508 reference - added P inside of most DIVs because vertical spacing was not displaying in preview. - Used dashes for 2nd level list items, to better distinguish for anyone using a screen reader. - Conformed white space.
- replace "requires" with "relies upon" editorial - Replaced use of single list item DL with blockquote. DT were just repeating the previous line, and blockquote is just as semantic as DD. - changed some DIV class assignments from NOTE to EXAMPLE - I removed paragraph breaks between HTML blocks, mostly because that is a problem for my agency repo. W3C repo probably is not as finicky. Preview (from markdown editor) has a little more fidelity.
What I tried to improve: - include definitions as something regulators should not tweak - have phrasing track literally to WCAG in a few more places
✅ Deploy Preview for wcag2ict ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Should close #329 |
|
@bruce I'm a bit worried about the scope of edits in this PR. Doesn't seem like any of them had anything to do with the topic for the PR which was to edit for the uses of "requires". Also, each file in this PR has some merge conflicts which makes this a complicated merge since it covers so many files. |
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
Co-authored-by: Mary Jo Mueller <maryjom@us.ibm.com>
|
@maryjom I concur with your changes and accepted/resolved conversation in each case.
They were all markdown files I was lead to from search of require/s/ed/ing on recent editors' draft. I regret that I did not take notes on how I came to target which files. I am concerned that I did not find all of the uses of requir* to review.
I have resolved the merge conflicts. Sadly, that is an exercise which I have some practice! |
| * [1.4.2 Audio Control](http://www.w3.org/TR/WCAG22/#audio-control); | ||
| * [2.1.2 No Keyboard Trap](http://www.w3.org/TR/WCAG22/#no-keyboard-trap); | ||
| * [2.2.2 Pause, Stop, Hide](http://www.w3.org/TR/WCAG22/#pause-stop-hide). | ||
| * [2.3.1 Three Flashes or Below Threshold](http://www.w3.org/TR/WCAG22/#three-flashes-or-below-threshold); | ||
|
|
||
| Also, as noted in the Introduction, it wasn't possible to unambiguously carve up software into discrete pieces, and so the unit of evaluation for non-web software is the whole software program. As with any software testing this can be a very large unit of evaluation, and methods similar to standard software testing might be used. | ||
| As noted in the [Introduction](#introduction), it isn’t possible to unambiguously divide software into discrete pieces. The unit of evaluation for non-web software is the whole software program. As with any software testing this can be a very large unit of evaluation, and methods similar to standard software testing may be used. |
There was a problem hiding this comment.
| As noted in the [Introduction](#introduction), it isn’t possible to unambiguously divide software into discrete pieces. The unit of evaluation for non-web software is the whole software program. As with any software testing this can be a very large unit of evaluation, and methods similar to standard software testing may be used. | |
| As noted in the [Introduction](#introduction), it isn’t possible to unambiguously divide software into discrete pieces. Therefore, the unit of evaluation for non-web software is the whole software program. As with any software testing this can be a very large unit of evaluation, and methods similar to standard software testing may be used. |
|
@maryjom -- I think this PR and related branch is OBE and can be deleted. |
@bruce-usab OBE? Does this mean outdated by your other PRs? |
|
This PR was overtaken by other more focused PRs. |
Still a work in progress...