- From: Kevin White <kevin@w3.org>
- Date: Mon, 30 Jan 2023 11:16:49 +0000
- To: "wai-eo-editors@w3.org" <wai-eo-editors@w3.org>
- Message-Id: <C3784C4C-E1B9-418A-A2B5-AC8A237F32E4@w3.org>
Hi All, I have taken a look at this and I think I know what the problem is. It seems that a number of the sample pages that were added have the same ID. I ran a test with the currently live tool and the assigned IDs are unique. When I manually changed the sample ID and then imported the modified JSON I could replicate the issue. There are a couple of peculiarities though: I have no idea how Nicki’s team managed to have a JSON file with a) duplicate IDs and b) IDs that were URLs. The current tool assigns a unique ID of the form ’subject_\d+’. The JSON that Nicki sent had IDs that matched the URL in the sample description. There is a difference between the current live version of the tool and the version that I cloned that I cannot work out. I noticed this because the two behave slightly differently when dealing with the non-unique IDs. The live side exhibits the issue that Nicki reported: URLs get changed to ‘h’. The clone site from the master branch simply displays the last sample in the structuredSample order. Would love to get to the bottom of some of these questions so that I can respond to Nicki. Kevin > On 30 Jan 2023, at 06:16, Berry Nicki Digital Group Quarry House <Nicki.Berry@dwp.gov.uk> wrote: > > Hi > > The attached file is the JSON file I downloaded after working on an audit report. If you go to the Select Sample page, I had originally input 20 pages with full URLs. It cut this down to 11 pages and many of the URLs got changed to ‘h’. We tried it many times, saving the JSON file on local drive, OneDrive, SharePoint, etc. Nothing helped. > > Eventually, I decided to just fill it all in during one long session After working on it for several hours, I clicked one of the – buttons to close the Time-based media section (as the product didn’t have any). That caused the page to crash and apart from the HTML file I had, I lost everything. I ended up working in VS Code, using the HTML file I had previously exported. > > Hope this helps, > > Thanks > > Nicki > > Nicki Berry | Head of Accessibility | Accessibility Standards and Strategy | Department for Work and Pensions | Digital Group | Quarry House, Leeds, LS2 7UE | Tel: 0300 087 8667 |nicki.berry@dwp.gov.uk <mailto:nicki.berry@dwp.gov.uk> | accessibility-manual.dwp.gov.uk <http://www.accessibility-manual.dwp.gov.uk/> > Please consider the environment before printing > > Preferred terminology: wheelchair user, assistance dog, disabled person > > From: Kevin White <kevin@w3.org> > Sent: 27 January 2023 09:32 > To: Berry Nicki Digital Group Quarry House <Nicki.Berry@dwp.gov.uk> > Cc: wai-eo-editors@w3.org > Subject: Re: [en] WCAG-EM Report Tool > > Hi Nicki, > > Thanks for getting in touch. I am not aware of this as a known issue. Do you have a sample JSON file that you could share that could be used to replicate the problem? > > Thanks > > Kevin > > > On 26 Jan 2023, at 06:45, Berry Nicki Digital Group Quarry House <Nicki.Berry@dwp.gov.uk <mailto:Nicki.Berry@dwp.gov.uk>> wrote: > > Hi > We have had several times where the JSON file has not loaded correctly and the some of the sample web pages have disappeared. Also for those that remain, the URLs have been changed, often just leaving the letter ‘h’. This is causing frustration as we keep having to start the whole report again. > Is this a known issue? > Thanks > Nicki > > Nicki Berry | Head of Accessibility | Accessibility Standards and Strategy | Department for Work and Pensions | Digital Group | Quarry House, Leeds, LS2 7UE | Tel: 0300 087 8667 |nicki.berry@dwp.gov.uk <mailto:nicki.berry@dwp.gov.uk> | accessibility-manual.dwp.gov.uk <http://www.accessibility-manual.dwp.gov.uk/> > Please consider the environment before printing > > Preferred terminology: wheelchair user, assistance dog, disabled person > > > ********************************************************************** > This document is strictly confidential and is intended only for use by the addressee. > If you are not the intended recipient any disclosure, copying, distribution > or other action taken in reliance of the information contained in this email is strictly prohibited. > > Any views expressed by the sender of this message are not necessarily those of the Department > for Work and Pensions. > If you have received this transmission in error please tell us and then permanently delete > what you have received. > This email was scanned for viruses by the Department for Work and Pensions antivirus services and was found to be virus free. > Please note: Incoming and outgoing email messages are routinely monitored for compliance with our Email Policy. > ********************************************************************** > > ********************************************************************** > This document is strictly confidential and is intended only for use by the addressee. > If you are not the intended recipient any disclosure, copying, distribution > or other action taken in reliance of the information contained in this email is strictly prohibited. > > Any views expressed by the sender of this message are not necessarily those of the Department > for Work and Pensions. > If you have received this transmission in error please tell us and then permanently delete > what you have received. > This email was scanned for viruses by the Department for Work and Pensions antivirus services and was found to be virus free. > Please note: Incoming and outgoing email messages are routinely monitored for compliance with our Email Policy. > **********************************************************************<careers-toolbox-evaluation (4).json>
Received on Monday, 30 January 2023 11:16:53 UTC