W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2012

Re: SV: SV: SV: in-page text-to-speech

From: Wayne Dick <wayneedick@gmail.com>
Date: Thu, 16 Aug 2012 15:05:25 -0700
Message-ID: <CAJeQ8SAmYPnLV35-5TGaeXc7Cg6UnVoBUqqF62grZohnJoDLmA@mail.gmail.com>
To: Brian Cragun <cragun@us.ibm.com>
Cc: w3c-wai-ig@w3.org
If Sweden or any other country requires in-page text-to-speech or
in-page text-enlargement then this is a major departure from standards
harmonization.  It really opens the door to inaccessible sites that
provide inadequate accessibility support.

Put your effort in WCAG 2.0 Level AA compliance.  Text-to-speech works
on a WCAG 2.0 Level AA site, and text-only enlargement is available to
a greater extent than any in-page enlargement provides.

We really don't need to invent unnecessary jobs for developers.  In
the US there is absolutely no such requirement.  Also, if you have a
site with in-page accommodation that fails WCAG the sight is
inaccessible.

Wayne

On 8/16/12, Brian Cragun <cragun@us.ibm.com> wrote:
> Thank you, Morten,
>
> This is very helpful.
>
> Regards,
>
> Brian
>
>
>
>
>
> Brian Cragun
> IBM AbilityLab Consultant
> IBM Master Inventor
> IBM Research
> Tel: 720-663-2801
> E-mail: cragun@us.ibm.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From:   "Morten Tollefsen" <morten@medialt.no>
> To:     Brian Cragun/Rochester/IBM@IBMUS,
> Cc:     "Adam Cooper" <cooperad@bigpond.com>, "Harry Loots"
> <harry.loots@ieee.org>, "Patrick H. Lauke" <redux@splintered.co.uk>,
> <w3c-wai-ig@w3.org>
> Date:   08/16/2012 02:43 AM
> Subject:        SV: SV: SV: in-page text-to-speech
>
>
>
> Hi!
>
> I got the following answer from Rudolph Brynn (Standards Norway):
>
> ----------
> 1)  These are required for "public institutions".  I assume that means
> government, including schools.  Obviously it is not required but
> recommended for business.  Does the requirement extend to any other
> entities?
>
> It is primarily for public institutions, meaning on government, county and
> municipal levels. But also recommendations for private enterprises, I
> would assume in particular those in touch with the public authorities in
> public procurement contracts.
>
> 2)  I understand these to be requirements.   What happens if the
> requirements are not met.  Are there laws associated with the
> requirements?  Or are these more like guidelines?
>
> They are guidelines for public authorities, not legal acts nor standards.
> They have no legal effect as Sweden has not an accessibility act like
> Norway but follow the EU regulations on public procurements, which
> requires design for all to be part of planning/technical specifications
> concerning tenders. Only the Swedish standardisation body, SIS may publish
> regular standards, be they national (SS), European (EN) or international
> (ISO). As in Norway.
>
>
> 3)  Can you help me understand what the difference is between Priority 1
> and Priority 2?  Is Priority 1 mandatory, and Priority 2 optional?
>
> I understand it is a matter of importance, you should definitely implement
> the Priority 1, then P2 and then P3 - but refer to the other answers.
>
>
> 4)  Further when I look at the requirement for TTS on R11, it uses the
> (translated word) Recommendation for TTS, instead of requirement.  Can you
> help me understand how mandatory the TTS requirement is?
>
> Like the other parts of the guideline, a recommendation. Only if a Swedish
> legal act refers to the guidelines/standards related to them, we talk of
> requirements.
> ----------
>
> Priorities: What Rudolph writes above is probably correct. The only
> explanation I've found is:
> "Prioritet 1 till 3. Riktlinjerna har getts en prioritet från 1 till 3. Om
> ni behöver prioritera börja med de riktlinjer som har prioritet 1.
> Därefter kan riktlinjerna med prioritet 2 och 3 hanteras."
> My translation:
> Priority 1 to 3 The guidelines have been given priorities from 1 to 3. If
> you have to prioritize start with the priority 1 guidelines and thereafter
> continue with the priority 2 and 3 guidelines.
>
> - Morten
>
> Fra: Brian Cragun [mailto:cragun@us.ibm.com]
> Sendt: 15. august 2012 15:30
> Til: Morten Tollefsen
> Kopi: Adam Cooper; Harry Loots; Patrick H. Lauke; w3c-wai-ig@w3.org
> Emne: Re: SV: SV: in-page text-to-speech
>
> Morton,
>
> Thanks for the links.  With Google Translate, (and some very rusty Danish
> skills) I think I understand most of this.  May I ask some clarifying
> questions?  (To help me understand detail that is not quite coming through
> the translation. )
>
> 1)  These are required for "public institutions".  I assume that means
> government, including schools.  Obviously it is not required but
> recommended for business.  Does the requirement extend to any other
> entities?
>
> 2)  I understand these to be requirements.   What happens if the
> requirements are not met.  Are there laws associated with the
> requirements?  Or are these more like guidelines?
>
> 3)  Can you help me understand what the difference is between Priority 1
> and Priority 2?  Is Priority 1 mandatory, and Priority 2 optional?
>
> 4)  Further when I look at the requirement for TTS on R11, it uses the
> (translated word) Recommendation for TTS, instead of requirement.  Can you
> help me understand how mandatory the TTS requirement is?
> Regards,
>
> Brian
>
> ________________________________________
>
> Brian Cragun
> IBM AbilityLab Consultant
> IBM Master Inventor
> IBM Research
> Tel: 720-663-2801
> E-mail: cragun@us.ibm.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ________________________________________
>
>
>
>
>
>
> From:        "Morten Tollefsen" <morten@medialt.no>
> To:        Brian Cragun/Rochester/IBM@IBMUS,
> Cc:        "Adam Cooper" <cooperad@bigpond.com>, "Harry Loots"
> <harry.loots@ieee.org>, "Patrick H. Lauke" <redux@splintered.co.uk>,
> <w3c-wai-ig@w3.org>
> Date:        08/15/2012 03:22 AM
> Subject:        SV: SV: in-page text-to-speech
> ________________________________________
>
>
>
> Hi, Brian!
>
> Of course, here it is:
> http://www.webbriktlinjer.se/
> As far as I have been able to figure out this is a standard.
>
> I’ve commented a little bit, but this is in Norwegian and is therefore
> probably not very interesting/useful:
> http://medialt.no/vgledningen-fr-webbutveckling/1175.aspx
>
> BR: Morten Tollefsen
> www.medialt.no, +47 908 99 305
>
> Fra: Brian Cragun [mailto:cragun@us.ibm.com]
> Sendt: 14. august 2012 15:45
> Til: Morten Tollefsen
> Kopi: Adam Cooper; Harry Loots; Patrick H. Lauke; w3c-wai-ig@w3.org
> Emne: Re: SV: in-page text-to-speech
>
> Morten,
>
> Can you please provide a reference to the Swedish standard you speak of?
>  And, is it just a recommendation or a standard?
> Regards,
>
> Brian
>
>
> ________________________________________
>
> Brian Cragun
> IBM AbilityLab Consultant
> IBM Master Inventor
> IBM Research
> Tel: 720-663-2801
> E-mail: cragun@us.ibm.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ________________________________________
>
>
>
>
>
>
> From:        "Morten Tollefsen" <morten@medialt.no>
> To:        "Harry Loots" <harry.loots@ieee.org>, "Adam Cooper"
> <cooperad@bigpond.com>,
> Cc:        "Patrick H. Lauke" <redux@splintered.co.uk>,
> <w3c-wai-ig@w3.org>
> Date:        08/14/2012 05:19 AM
> Subject:        SV: in-page text-to-speech
> ________________________________________
>
>
>
>
> Hi, Harry!
>
> I totally agree.
>
> In some new Swedish guidelines for web developments (only public
> authorities have to follow these) accessibility is one of the categories.
> The first guideline say: follow WCAG 2. The other 43 accessibility
> guidelines cover forms, languages, links and other things. In one of the
> guidelines it is stated that talking websites are required! I was quite
> surprised when I read this! If I counted correctly, 33 of the 44
> guidelines in the accessibility section are also found under usability☺!
>
> Morten
>
>
>
Received on Thursday, 16 August 2012 22:05:54 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:30 UTC