W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13442] Clarify cases that should NOT be "non-interactive presentation user agents"

From: <bugzilla@jessica.w3.org>
Date: Thu, 11 Aug 2011 06:25:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QrOiB-0005pz-Uv@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WONTFIX

--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-11 06:25:47 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:

Status: Rejected
Change Description: no spec change

If someone writes a program that converts HTML files to PDF files, and has a
"preview" mode that shows the PDF file, it is an interactive program that
accepts user input, but it would still just be a non-interactive presentation
user agent, and that would not be inappropriate (on the contrary, it would make
no sense for such an application to be any other conformance class). So I don't
think the "should" you are suggesting is an appropriate requirement.

At the end of the day, a developer writing an application so limited in scope
that they only designed it for one input modality isn't going to be swayed by
this section. Imelda should just switch to a better vendor (of which there are

Note also that making the sample limited applications you describe accessible
is much easier than making it support the entire suite of HTML APIs and
interaction features. What you are suggesting would require that the
application that displays a static Web-based slide also support interactive
HTML form controls, which sounds like it would be way out of the scope of what
such an application should be doing.

Just because you're not a full Web browser doesn't mean you shouldn't be
accessible. Any commercial application on a general purpose computer should be
accessible to all users of that computer, that's got nothing to do with the
HTML spec and everything to do with simple ethics and common sense.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 11 August 2011 06:26:44 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:16 UTC