639971 - Serve VPAT for the latest version of Firefox

Status: RESOLVED INCOMPLETE

(www.mozilla.org :: Pages & Content, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

We should try to update this before the release.

Comment 1

[Marco Zehe (:MarcoZ)]

One thing we should note in the FF4 VPAt is that Tab Groups/Panorama isn't accessible, but that working with tabs in the original sense isn't impaired. Jotting this down here as a reminder since it immediately sprang to mind.

Comment 2

[mcbmoz]

I'd like to redirect the following pages from the /firefox site to wherever you deploy this:

http://www.mozilla.org/en-US/firefox/vpat-1.5.html
http://www.mozilla.org/en-US/firefox/vpat-2.html
http://www.mozilla.org/en-US/firefox/vpat-3.html

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

What we might need to do is remove the version number off the vpat, and simple have a most recent document modification date (and do our best to keep it up to date against the latest FF release version). Marco can you think of issues with this approach?

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

Hi Marco, looking for feedback on comment 3.

Comment 5

[Marco Zehe (:MarcoZ)]

I have no problems with this approach. The changes usually aren't that drastic, so this should work.

Comment 6

[David Bolter [:davidb] (NeedInfo me for attention)]

OK then I propose the following. Change the top info to:

    Date: Current
    Name of Product: Firefox for desktop
    General Comments: Information in this VPAT is relevant to Firefox running on Windows operating systems prior to Windows 8. Additional developer tools exist in this product that are not installed by default. These optional tools have not been tested.

We can take snapshots for ESR releases. I don't have access to make these changes myself.

Comment 8

[Kohei Yoshino [:kohei]]

Why not move the VPAT to MDN? It's easier to update wiki pages than to edit static pages on www.mozilla.org.

Comment 9

[Marco Zehe (:MarcoZ)]

(In reply to Kohei Yoshino [:kohei] from comment #8)
> Why not move the VPAT to MDN? It's easier to update wiki pages than to edit
> static pages on www.mozilla.org.

I have no problem with this in principle, however since this is a semi-official document, I don't know if this will get us in any trouble. And since the VPAT is primarily used in the U.S., and maybe in Canada, someone familiar with the juristictional implications should answer this. David, can you think of anyone who might know if a Wiki page would be acceptable?

Comment 10

[David Bolter [:davidb] (NeedInfo me for attention)]

Maybe Jennison?

Comment 11

[Kohei Yoshino [:kohei]]

Alternatively we can move the VPAT docs to the new Bedrock platform from the legacy PHP site. So everyone can send pull requests to GitHub to update those docs easily.

Comment 12

[David Bolter [:davidb] (NeedInfo me for attention)]

(In reply to Kohei Yoshino [:kohei] from comment #11)
> Alternatively we can move the VPAT docs to the new Bedrock platform from the
> legacy PHP site. So everyone can send pull requests to GitHub to update
> those docs easily.

That sounds good to me.

Comment 13

[Kohei Yoshino [:kohei]]

I can help to move the older VPAT docs to Bedrock (if needed) but we still need the latest doc anyway. Can someone write it?

Comment 14

[Kohei Yoshino [:kohei]]

Do you have a draft for the Firefox 4+ VPAT?

Comment 15

[David Bolter [:davidb] (NeedInfo me for attention)]

Unfortunately I'm not aware of any updates since 3.6.

Comment 16

[Kohei Yoshino [:kohei]]

Updating the summary...

Comment 17

[Kohei Yoshino [:kohei]]

Closing since the new VPAT is not available yet. Please reopen once it's ready.