Re: [Conformance] Thoughts/ edits on the Use Cases Document

In the cryptocurrency apps the crypto price changes so fast there are some
things that would not apply, for example it is not possible to comply with
Timeout criteria when the user is about to buy because they can only
maintain the price for 5 seconds. On the other hand, on each cryptocurrency
information panel prices change at a pace of 1 or 2 seconds, so as soon as
a price is announced a lot of new prices are shown.

El mié, 27 jul 2022 a las 19:08, Jeanne Spellman (<
jspellman@spellmanconsulting.com>) escribió:

> Susana,
>
> What about cryptocurrency apps would make it hard to conform?  I think the
> apps should conform, and the data is just the data, but perhaps I am not
> seeing the bigger picture.
>
> jeanne
> On 7/27/2022 12:55 PM, Susana Pallero wrote:
>
> Hi team,
>
> I would like your opinion about if data that is updated at a fast pace
> (such as cryptocurrency apps) would be part of the Use Cases.
>
> Thanks,
> Regards,
>
>
> El vie, 13 may 2022 a las 15:59, Bruce Bailey (<Bailey@access-board.gov>)
> escribió:
>
>> We had a similar issue/concern for “raw data” with the Revised 508
>> Standards.  Jeanne, can you suggest a wiki or GitHub page where I might
>> share/memorialize some of that experience?
>>
>>
>>
>> The issue comes up in Technical Assistance in that if the business need
>> is, for example, an mpeg file format – that does not include captioning.
>> For federal agencies under 508, we point to the allowance for “fundamental
>> alteration”:
>>
>> https://www.access-board.gov/ict/#E202.6
>>
>>
>>
>> As Andy notes, any prepared product would need captioning.  Drawing the
>> line for public facing raw data gets pretty tricky pretty fast.  Is the
>> agency really only posting B-roll stuff?  If it worth sharing, why is not
>> also worth providing some kind of timed-text file?  During the 508 public
>> comment period, there were conversations about exceptions for “drafts” and
>> “works in progress” and the Access Board ultimately came to the conclusion
>> that would have been too much of a loophole.
>>
>>
>>
>> Still there are a couple of additional notable caveats related to the
>> limits of file formats:
>>
>>
>>
>> https://www.access-board.gov/ict/#504.1 Authoring Tools, General
>>
>> …to the extent that information required for accessibility is supported
>> by the destination format.
>>
>>
>>
>> https://www.access-board.gov/ict/#504.2 Content Creation or Editing
>>
>> …to file formats supported by the authoring tool.
>>
>> --
>> Bruce Bailey (he/him)
>> Accessibility IT Specialist
>> U.S. Access Board
>> 1331 F Street NW, Suite 1000
>> Washington, DC  20004-1111
>> 202-760-1947 (mobile)
>> bailey@access-board.gov
>>
>> Thank you for your questions concerning section 508 of the Rehabilitation
>> Act Amendments of 1998.  Section 508 authorizes the Access Board to provide
>> technical assistance to individuals and Federal departments and agencies
>> concerning the requirements of this section.  Technical assistance provided
>> in this email is intended solely as informal guidance; it is neither a
>> determination of your legal rights or responsibilities, nor a statement of
>> the official views of the U.S. Access Board or any other federal agency.
>> Any links to non-federal websites are provided as a courtesy and do not
>> represent an endorsement of the linked information, products, or services.
>>
>>
>>
>> *From:* Andrew Somers <andy@generaltitles.com>
>> *Sent:* Thursday, May 12, 2022 6:15 PM
>> *To:* Gregg Vanderheiden <gregg@raisingthefloor.org>
>> *Cc:* Silver TF <public-silver@w3.org>; Jeanne Spellman <
>> jspellman@spellmanconsulting.com>
>> *Subject:* Re: [Conformance] Thoughts/ edits on the Use Cases Document
>>
>>
>>
>> Hi Gregg, this is good and examines a useful array of use cases and
>> exceptions/qualifiers.
>>
>>
>>
>> *A potential “raw data” exception:*
>>
>>
>>
>> Something I mentioned in a related thread some months ago, relates to
>> “original data” for example:
>>
>>
>>
>> Camera original .mov, .avi or similar movie files are often important to
>> be kept as-is and unaltered, for evidentiary purposes for example.
>> Embedding things like caption data (into the file) typically results in the
>> file being re-compressed, which results in data loss. As such, a reasonable
>> exception to the captioning requirement relates to camera original files
>> which reasonably need to be left in their unaltered form.
>>
>>
>>
>> Caption files can be created as sidecars, of course—and naturally, a
>> separate version of the video file can be created to make captions
>> available, but consider a site such as WikiLeaks, where information that is
>> socially/politically important is held for dissemination. It is better that
>> a site be able to hold a mass of such data than to be prohibited from doing
>> so due to a compliance issue. And when possible, evidentiary data is best
>> held/provided in an unaltered form.
>>
>>
>>
>> Naturally, a commercial news operation should not be able to use such an
>> exception when it comes to their *prepared* newscasts, but even a
>> commercial news operation should be able to provide raw/unaltered footage
>> as a separately available file, and “raw” files can not reasonably be
>> required to be altered.
>>
>>
>>
>> As such, this points to needed exception language for raw, original, and
>> archival materials.
>>
>>
>>
>>
>>
>> Andy
>>
>>
>>
>> *   Andrew Somers *
>>
>> Senior Color Science Researcher
>>
>> *PerceptEx Perception Research Project*
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.myndex.com%2Fperceptex%2F&data=05%7C01%7Cbailey%40access-board.gov%7C24429574ac5d463f070508da34652ca7%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C1%7C637879906410328795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wlSXdOP6u%2Fo9%2FSjFGaBqCy%2BL1S5dKuJS6ZCz98g8lyA%3D&reserved=0>
>>
>>
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.myndex.com%2Fperceptex%2F&data=05%7C01%7Cbailey%40access-board.gov%7C24429574ac5d463f070508da34652ca7%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C1%7C637879906410328795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=wlSXdOP6u%2Fo9%2FSjFGaBqCy%2BL1S5dKuJS6ZCz98g8lyA%3D&reserved=0>
>>
>>
>>
>> On May 12, 2022, at 1:54 PM, Gregg Vanderheiden <
>> gregg@raisingthefloor.org> wrote:
>>
>>
>>
>> This is a work in progress —
>>
>>
>>
>> I’m posting it for review and feedback as I go
>>
>>
>>
>> <Use Cases for WCAG 3.0 Conformance.docx>
>>
>>
>>
>> gregg
>>
>> ———————————
>> Professor, University of Maryland, College Park
>> Founder and Director Emeritus , Trace R&D Center, UMD
>>
>> Co-Founder Raising the Floor. http://raisingthefloor.org
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fraisingthefloor.org%2F&data=05%7C01%7Cbailey%40access-board.gov%7C24429574ac5d463f070508da34652ca7%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C1%7C637879906410328795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=d8xWC1QMPOAjUXxeWOPS1J9dQGRVeQr9ZamSWBF%2FDbs%3D&reserved=0>
>> The Global Public Inclusive Infrastructure (GPII) http://GPII.net
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpii.net%2F&data=05%7C01%7Cbailey%40access-board.gov%7C24429574ac5d463f070508da34652ca7%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C1%7C637879906410328795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Pub5KexK8zMA7BTH%2Bds5qMMEhBy2kUPTlF%2B%2FepUu6%2Bo%3D&reserved=0>
>> The Morphic project  https://morphic.org
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmorphic.org%2F&data=05%7C01%7Cbailey%40access-board.gov%7C24429574ac5d463f070508da34652ca7%7Cfc6093f5e55e4f93b2cf26d0822201c9%7C0%7C1%7C637879906410328795%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5ZWWF56xiDN%2B%2BCRw3N5t5NVh08ht0z7t38d6nuKV1yY%3D&reserved=0>
>>
>>
>>
>>
>>
>

Received on Wednesday, 27 July 2022 18:02:50 UTC