Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

added interuptions #98

Closed
wants to merge 1 commit into from
Closed

added interuptions #98

wants to merge 1 commit into from

Conversation

lseeman
Copy link
Contributor

@lseeman lseeman commented Jan 30, 2017

and the glossary for easily availible

and the glossary for easily availible
@awkawk
Copy link
Member

awkawk commented Feb 5, 2017

@lseeman can you confirm that this is related to Issue 47?

@lseeman
Copy link
Contributor Author

lseeman commented Feb 5, 2017

yes. (as much as i can follow this)

@moekraft
Copy link

moekraft commented Feb 14, 2017

  • Editorial: There is an extra character between "an" and "example", i.e. or "involve anֲ emergency" in the Interruptions (minimum) section. Should this be a link to the definition for "emergency" as we have in the Interruptions section.

@awkawk
Copy link
Member

awkawk commented Feb 14, 2017

Pull request on #47 topic.

@awkawk awkawk mentioned this pull request Feb 14, 2017
<section class="sc">
<h4>Interruptions (minimum)</h4>
<p class="conformance-level">AA</p>
<p>There is an easily available mechanism to postpone and suppress interruptions and changes in content unless they are initiated by the user or involve anֲ emergency.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the word "and" is used between postpone and suppress, the literal meaning would be that postponing the interruption is required, i.e. the mechanism must make the interruption reappear. I'm assuming this is not the intent. If so, I would recommend changing to "postpone or permanently suppress" to make the options clear.

Also, if postponing is an option, I'd highly recommend requiring a minimum time before the interruption reappears.

<ul>
<li>can be set one time with as wide a scope as possible (such as using the standards of the OS, From ISO 9241-112 or GPII when available) </li>
<li>has the option to save or change the setting, where available interoperably, but also for the scope of the set of web pages </li>
<li>is reachable from each screen where it may be needed, and the path and the control conforms to all of this document</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Replace "screen" with "webpage", which has an existing glossary definition
  • Delete "and the path and control conforms to all of this document". This is not only implied in my opinion, but also does not specify a conformance level and conflicts/overlaps with Note 2 in the definition of mechanism.
  • "Reachable" is not defined and so this requirement is very vague. Technically, if I need to click Settings and then jump through 10 pages of controls to get to the mechanism for suppressing the interruption, that is reachable.

If the intent here is to be able to suppress with a single click, then maybe something like: "able to be set without any change of content".

<dd>
<ul>
<li>can be set one time with as wide a scope as possible (such as using the standards of the OS, From ISO 9241-112 or GPII when available) </li>
<li>has the option to save or change the setting, where available interoperably, but also for the scope of the set of web pages </li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latter part of this requirement is dangling (i.e. "but also..." only contains a prepositional phrase). I'd like to help with rewording, but I'm confused by the intent of this bullet versus the previous one. They both seem to be dealing with scope of the setting. Can you clarify the distinction?

<dt><dfn>easily available (or easily available mode or setting) one or more of the following are true:</dfn></dt>
<dd>
<ul>
<li>can be set one time with as wide a scope as possible (such as using the standards of the OS, From ISO 9241-112 or GPII when available) </li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the spirit of accessibility, expand the acronyms for OS and GPII.

@michael-n-cooper
Copy link
Member

Addressed by 2705d25. Got some of the editorial comments but not the more substantial ones. Further process of #47 should come back to this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants