508 Software Tester Software Coding Advice for Software Developers

[Russell, Jon (CTR)]

Can we start a database somehow contained is an area on this archive - like a wiki site - or somewhere else on the WAI site for:

508 Software Tester Software Coding Advice for Software Developers - (as software testers find bugs/issues?)

Thanks,

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 - 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov

[Emily Ogle]

I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.

Emily Ogle

508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)
Thanks,
Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]

[Chaals Nevile]

It is certainly possible to do this.

It is, as I understand it, the intention of the techniques documents to
provide this information. One of the problems is getting people who have
dealt with something not covered there already to actually provide the
content so it can be added.

cheers

Chaals

Post by Emily Ogle
I know my organization has struggled with the challenges of developing
accessible software, so I would find a resource quite helpful, though it

Post by Emily Ogle
wouldn’t necessarily need to be just Section 598, as EN 301 549 covers

Section 508 and then some.
Emily Ogle
On May 3, 2018, at 10:32 AM, Russell, Jon (CTR)

Post by Emily Ogle
Can we start a database somehow contained is an area on this archive –
508 Software Tester Software Coding Advice for Software Developers –
(as software testers find bugs/issues?)
Thanks,
Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]

[Katie Haritos-Shea]

The requirements for software in Section 508 have requirements that are
above and beyond WCAG 2.0. Specifically, there are additional requirements
for authoring tools, browsers, OSs, and media players, and (what is defined
as) applications, and it depends upon the location of the software (public
facing, web-based, AOC, and non-web-based).

Post by Chaals Nevile
It is certainly possible to do this.
It is, as I understand it, the intention of the techniques documents to
provide this information. One of the problems is getting people who have
dealt with something not covered there already to actually provide the
content so it can be added.
cheers
Chaals
I know my organization has struggled with the challenges of developing
accessible software, so I would find a resource quite helpful, though it
wouldn’t necessarily need to be just Section 598, as EN 301 549 covers
Section 508 and then some.
Emily Ogle
On May 3, 2018, at 10:32 AM, Russell, Jon (CTR) <
Can we start a database somehow contained is an area on this archive –
508 Software Tester Software Coding Advice for Software Developers – (as
software testers find bugs/issues?)
Thanks,
*Jon Russell*
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
--
Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?

[Chaals Nevile]

Post by Katie Haritos-Shea
The requirements for software in Section 508 have requirements that are
above and beyond WCAG 2.0.

Oh, true.

Post by Katie Haritos-Shea
Specifically, there are additional requirements for authoring tools,
browsers, OSs, and media players,

Hmm. Aside from OS requirements (I'm going to guess that in this case
nobody was building one, but let's not forget that people are), those
would be fair game for ATAG and UAAG techniques respectively.

There seems to be no group formally chartered to deal with those, but it
would be fair game for work within this Interest Group.

Different levels of requirement based on who does it is a compliance
issue, rather than an accessibility issue - as far as I can tell *any*
accessibility issue that impacts stuff on the Web is reasonable for
discussion in this group. I don't *know* of a better alternate forum for
stuff that impacts software that is not web-related, nor do I know if it
is a topic that this group would be OK hosting. Katie, do you have a
chair's opinion on that?

At any rate, for the specific question the best approach might be to
create a W3C community group - anyone can join that, and it offers the
necessary tools. If that would be helpful, I am making a concrete offer to
set up an open, collaborative workspace for collecting testing and
implementation techniques related to software accessibility, where sharing
work makes things easier in the long run.

Please note, for anyone who expects others to load it up with the answers
they have developed so they don't have to, I can pretty much guarantee a
high level of disappointment. Specifically, since I don't develop a lot of
software, and don't have a lot of spare time, haven't worked on software
required to comply with the refreshed 508, I don't currently have any
particular content to contribute. And if nobody else does either, this
will be a pretty empty and pointless effort.

Given 6 requests to do this, each accompanied by a commitment to provide
*at minimum* 500 words on specific testing or implementation techniques,
it's fairly trivial to set up (an hour or so). And given the commitments
made good, I'll put in some work to organise a framework for actually
collecting stuff, which is somewhat more complicated...

cheers

cheers

Chaals

Post by Katie Haritos-Shea
and (what is defined as) applications, and it depends upon the location
of the software (public facing, web-based, AOC, and non-web-based).

Post by Chaals Nevile
It is certainly possible to do this.
It is, as I understand it, the intention of the techniques documents to
provide this information. One of the problems is getting people who
have >>dealt with something not covered there already to actually
provide the content so it can be added.
cheers
Chaals

Post by Emily Ogle
I know my organization has struggled with the challenges of developing
accessible software, so I would find a resource quite helpful, though
it >>>wouldn’t necessarily need to be just Section 598, as EN 301 549
covers Section 508 and then some.
Emily Ogle
On May 3, 2018, at 10:32 AM, Russell, Jon (CTR)

Post by Russell, Jon (CTR)
Can we start a database somehow contained is an area on this archive
508 Software Tester Software Coding Advice for Software Developers –
(as software testers find bugs/issues?)
Thanks,
Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]

--Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?

[Emily Ogle]

I would get a lot of value from such a group. I’d be happy to share my own experiences so far.

The requirements for software in Section 508 have requirements that are above and beyond WCAG 2.0.
Oh, true.
Specifically, there are additional requirements for authoring tools, browsers, OSs, and media players,
Hmm. Aside from OS requirements (I'm going to guess that in this case nobody was building one, but let's not forget that people are), those would be fair game for ATAG and UAAG techniques respectively.
There seems to be no group formally chartered to deal with those, but it would be fair game for work within this Interest Group.
Different levels of requirement based on who does it is a compliance issue, rather than an accessibility issue - as far as I can tell *any* accessibility issue that impacts stuff on the Web is reasonable for discussion in this group. I don't *know* of a better alternate forum for stuff that impacts software that is not web-related, nor do I know if it is a topic that this group would be OK hosting. Katie, do you have a chair's opinion on that?
At any rate, for the specific question the best approach might be to create a W3C community group - anyone can join that, and it offers the necessary tools. If that would be helpful, I am making a concrete offer to set up an open, collaborative workspace for collecting testing and implementation techniques related to software accessibility, where sharing work makes things easier in the long run.
Please note, for anyone who expects others to load it up with the answers they have developed so they don't have to, I can pretty much guarantee a high level of disappointment. Specifically, since I don't develop a lot of software, and don't have a lot of spare time, haven't worked on software required to comply with the refreshed 508, I don't currently have any particular content to contribute. And if nobody else does either, this will be a pretty empty and pointless effort.
Given 6 requests to do this, each accompanied by a commitment to provide *at minimum* 500 words on specific testing or implementation techniques, it's fairly trivial to set up (an hour or so). And given the commitments made good, I'll put in some work to organise a framework for actually collecting stuff, which is somewhat more complicated...
cheers
cheers
Chaals
and (what is defined as) applications, and it depends upon the location of the software (public facing, web-based, AOC, and non-web-based).

Post by Chaals Nevile
It is certainly possible to do this.
It is, as I understand it, the intention of the techniques documents to provide this information. One of the problems is getting people who have dealt with something not covered there already to actually provide the content so it can be added.
cheers
Chaals
I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.
Emily Ogle

508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)
Thanks,
Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]

--
Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?

--
Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?

[Russell, Jon (CTR)]

Challs – I see your concerns – and you are right – no one is going to pre-populate it – I have a little database (of files – links) I collect to provide for my software developers who I test for – I don’t “have to do it” – but I realize that the relationship between developer and tester can be tough – and since we testers are sort of code “critics” so to speak – the least we can do is help developers get to where they need to be – either as Emily says non-508 coding and 508 coding – just some wiki site or mail list or whatever something to search – sure it will be messy won’t be pretty – but just gold nuggets of clues and info to get us closer to doing coding right.

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov

From: Emily Ogle <***@yahoo.com>
Sent: Friday, May 4, 2018 1:14 PM
To: Chaals Nevile <***@yandex.ru>
Cc: WAI Interest Group <w3c-wai-***@w3.org>
Subject: Re: 508 Software Tester Software Coding Advice for Software Developers

I would get a lot of value from such a group. I’d be happy to share my own experiences so far.

On May 4, 2018, at 4:46 AM, Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
On Fri, 04 May 2018 04:18:59 +0200, Katie Haritos-Shea <***@gmail.com<mailto:***@gmail.com>> wrote:
The requirements for software in Section 508 have requirements that are above and beyond WCAG 2.0.

Oh, true.

Specifically, there are additional requirements for authoring tools, browsers, OSs, and media players,

Hmm. Aside from OS requirements (I'm going to guess that in this case nobody was building one, but let's not forget that people are), those would be fair game for ATAG and UAAG techniques respectively.

There seems to be no group formally chartered to deal with those, but it would be fair game for work within this Interest Group.

Different levels of requirement based on who does it is a compliance issue, rather than an accessibility issue - as far as I can tell *any* accessibility issue that impacts stuff on the Web is reasonable for discussion in this group. I don't *know* of a better alternate forum for stuff that impacts software that is not web-related, nor do I know if it is a topic that this group would be OK hosting. Katie, do you have a chair's opinion on that?

At any rate, for the specific question the best approach might be to create a W3C community group - anyone can join that, and it offers the necessary tools. If that would be helpful, I am making a concrete offer to set up an open, collaborative workspace for collecting testing and implementation techniques related to software accessibility, where sharing work makes things easier in the long run.

Please note, for anyone who expects others to load it up with the answers they have developed so they don't have to, I can pretty much guarantee a high level of disappointment. Specifically, since I don't develop a lot of software, and don't have a lot of spare time, haven't worked on software required to comply with the refreshed 508, I don't currently have any particular content to contribute. And if nobody else does either, this will be a pretty empty and pointless effort.

Given 6 requests to do this, each accompanied by a commitment to provide *at minimum* 500 words on specific testing or implementation techniques, it's fairly trivial to set up (an hour or so). And given the commitments made good, I'll put in some work to organise a framework for actually collecting stuff, which is somewhat more complicated...

cheers

cheers

Chaals

and (what is defined as) applications, and it depends upon the location of the software (public facing, web-based, AOC, and non-web-based).

On Thu, May 3, 2018, 8:55 PM Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
It is certainly possible to do this.

It is, as I understand it, the intention of the techniques documents to provide this information. One of the problems is getting people who have dealt with something not covered there already to actually provide the content so it can be added.

cheers

Chaals

On Thu, 03 May 2018 22:18:03 +0200, Emily Ogle <***@yahoo.com<mailto:***@yahoo.com>> wrote:

I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.

Emily Ogle

On May 3, 2018, at 10:32 AM, Russell, Jon (CTR) <***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>> wrote:
Can we start a database somehow contained is an area on this archive – like a wiki site – or somewhere else on the WAI site for:

508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)

Thanks,

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>
--
Chaals: Charles (McCathie) Nevile find more at https://yandex.com
Using Opera's long-abandoned mail client: http://www.opera.com/mail/
Is there really still nothing better?

[Sean Murphy (seanmmur)]

The wiki must go beyond just the web. Must include mobile, desktop and any other technologies. As there are major gaps in the other spaces where people with the knowledge if they are willing to share could close them. The true challenge is to get people to share their knowledge. The wiki must not focus on section 508, rather focus on accessibility technical standards to help the whole international community.

Regards
Sean Murphy
Accessibility Software ENGINEER
***@cisco.com
Tel: [phone]

Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com

http://www.cisco.com/go/accessibility

Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html


From: Russell, Jon (CTR) <***@associates.hq.dhs.gov>
Sent: Saturday, 5 May 2018 3:41 AM
To: Emily Ogle <***@yahoo.com>; Chaals Nevile <***@yandex.ru>
Cc: WAI Interest Group <w3c-wai-***@w3.org>
Subject: RE: 508 Software Tester Software Coding Advice for Software Developers

Challs – I see your concerns – and you are right – no one is going to pre-populate it – I have a little database (of files – links) I collect to provide for my software developers who I test for – I don’t “have to do it” – but I realize that the relationship between developer and tester can be tough – and since we testers are sort of code “critics” so to speak – the least we can do is help developers get to where they need to be – either as Emily says non-508 coding and 508 coding – just some wiki site or mail list or whatever something to search – sure it will be messy won’t be pretty – but just gold nuggets of clues and info to get us closer to doing coding right.

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>

From: Emily Ogle <***@yahoo.com<mailto:***@yahoo.com>>
Sent: Friday, May 4, 2018 1:14 PM
To: Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>>
Cc: WAI Interest Group <w3c-wai-***@w3.org<mailto:w3c-wai-***@w3.org>>
Subject: Re: 508 Software Tester Software Coding Advice for Software Developers

I would get a lot of value from such a group. I’d be happy to share my own experiences so far.

On May 4, 2018, at 4:46 AM, Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
On Fri, 04 May 2018 04:18:59 +0200, Katie Haritos-Shea <***@gmail.com<mailto:***@gmail.com>> wrote:
The requirements for software in Section 508 have requirements that are above and beyond WCAG 2.0.

Oh, true.

Specifically, there are additional requirements for authoring tools, browsers, OSs, and media players,

Hmm. Aside from OS requirements (I'm going to guess that in this case nobody was building one, but let's not forget that people are), those would be fair game for ATAG and UAAG techniques respectively.

There seems to be no group formally chartered to deal with those, but it would be fair game for work within this Interest Group.

Different levels of requirement based on who does it is a compliance issue, rather than an accessibility issue - as far as I can tell *any* accessibility issue that impacts stuff on the Web is reasonable for discussion in this group. I don't *know* of a better alternate forum for stuff that impacts software that is not web-related, nor do I know if it is a topic that this group would be OK hosting. Katie, do you have a chair's opinion on that?

At any rate, for the specific question the best approach might be to create a W3C community group - anyone can join that, and it offers the necessary tools. If that would be helpful, I am making a concrete offer to set up an open, collaborative workspace for collecting testing and implementation techniques related to software accessibility, where sharing work makes things easier in the long run.

Please note, for anyone who expects others to load it up with the answers they have developed so they don't have to, I can pretty much guarantee a high level of disappointment. Specifically, since I don't develop a lot of software, and don't have a lot of spare time, haven't worked on software required to comply with the refreshed 508, I don't currently have any particular content to contribute. And if nobody else does either, this will be a pretty empty and pointless effort.

Given 6 requests to do this, each accompanied by a commitment to provide *at minimum* 500 words on specific testing or implementation techniques, it's fairly trivial to set up (an hour or so). And given the commitments made good, I'll put in some work to organise a framework for actually collecting stuff, which is somewhat more complicated...

cheers

cheers

Chaals

and (what is defined as) applications, and it depends upon the location of the software (public facing, web-based, AOC, and non-web-based).

On Thu, May 3, 2018, 8:55 PM Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
It is certainly possible to do this.

It is, as I understand it, the intention of the techniques documents to provide this information. One of the problems is getting people who have dealt with something not covered there already to actually provide the content so it can be added.

cheers

Chaals

On Thu, 03 May 2018 22:18:03 +0200, Emily Ogle <***@yahoo.com<mailto:***@yahoo.com>> wrote:

I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.

Emily Ogle

On May 3, 2018, at 10:32 AM, Russell, Jon (CTR) <***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>> wrote:
Can we start a database somehow contained is an area on this archive – like a wiki site – or somewhere else on the WAI site for:

508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)

Thanks,

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>

[Russell, Jon (CTR)]

Yep – agreed – accessibility in general – a wiki that people provide examples – the user could do a search on the wiki to see if they can find what they need – messy but start a wiki database of accessibility knowledge --

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov

From: Sean Murphy (seanmmur) <***@cisco.com>
Sent: Sunday, May 6, 2018 11:12 PM
To: Russell, Jon (CTR) <***@associates.hq.dhs.gov>; Emily Ogle <***@yahoo.com>; Chaals Nevile <***@yandex.ru>
Cc: WAI Interest Group <w3c-wai-***@w3.org>
Subject: RE: 508 Software Tester Software Coding Advice for Software Developers

The wiki must go beyond just the web. Must include mobile, desktop and any other technologies. As there are major gaps in the other spaces where people with the knowledge if they are willing to share could close them. The true challenge is to get people to share their knowledge. The wiki must not focus on section 508, rather focus on accessibility technical standards to help the whole international community.

Regards
Sean Murphy
Accessibility Software ENGINEER
***@cisco.com
Tel: [phone]

Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com

http://www.cisco.com/go/accessibility

Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html


From: Russell, Jon (CTR) <***@associates.hq.dhs.gov>
Sent: Saturday, 5 May 2018 3:41 AM
To: Emily Ogle <***@yahoo.com>; Chaals Nevile <***@yandex.ru>
Cc: WAI Interest Group <w3c-wai-***@w3.org>
Subject: RE: 508 Software Tester Software Coding Advice for Software Developers

Challs – I see your concerns – and you are right – no one is going to pre-populate it – I have a little database (of files – links) I collect to provide for my software developers who I test for – I don’t “have to do it” – but I realize that the relationship between developer and tester can be tough – and since we testers are sort of code “critics” so to speak – the least we can do is help developers get to where they need to be – either as Emily says non-508 coding and 508 coding – just some wiki site or mail list or whatever something to search – sure it will be messy won’t be pretty – but just gold nuggets of clues and info to get us closer to doing coding right.

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>

From: Emily Ogle <***@yahoo.com<mailto:***@yahoo.com>>
Sent: Friday, May 4, 2018 1:14 PM
To: Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>>
Cc: WAI Interest Group <w3c-wai-***@w3.org<mailto:w3c-wai-***@w3.org>>
Subject: Re: 508 Software Tester Software Coding Advice for Software Developers

I would get a lot of value from such a group. I’d be happy to share my own experiences so far.

On May 4, 2018, at 4:46 AM, Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
On Fri, 04 May 2018 04:18:59 +0200, Katie Haritos-Shea <***@gmail.com<mailto:***@gmail.com>> wrote:
The requirements for software in Section 508 have requirements that are above and beyond WCAG 2.0.

Oh, true.

Specifically, there are additional requirements for authoring tools, browsers, OSs, and media players,

Hmm. Aside from OS requirements (I'm going to guess that in this case nobody was building one, but let's not forget that people are), those would be fair game for ATAG and UAAG techniques respectively.

There seems to be no group formally chartered to deal with those, but it would be fair game for work within this Interest Group.

Different levels of requirement based on who does it is a compliance issue, rather than an accessibility issue - as far as I can tell *any* accessibility issue that impacts stuff on the Web is reasonable for discussion in this group. I don't *know* of a better alternate forum for stuff that impacts software that is not web-related, nor do I know if it is a topic that this group would be OK hosting. Katie, do you have a chair's opinion on that?

At any rate, for the specific question the best approach might be to create a W3C community group - anyone can join that, and it offers the necessary tools. If that would be helpful, I am making a concrete offer to set up an open, collaborative workspace for collecting testing and implementation techniques related to software accessibility, where sharing work makes things easier in the long run.

Please note, for anyone who expects others to load it up with the answers they have developed so they don't have to, I can pretty much guarantee a high level of disappointment. Specifically, since I don't develop a lot of software, and don't have a lot of spare time, haven't worked on software required to comply with the refreshed 508, I don't currently have any particular content to contribute. And if nobody else does either, this will be a pretty empty and pointless effort.

Given 6 requests to do this, each accompanied by a commitment to provide *at minimum* 500 words on specific testing or implementation techniques, it's fairly trivial to set up (an hour or so). And given the commitments made good, I'll put in some work to organise a framework for actually collecting stuff, which is somewhat more complicated...

cheers

cheers

Chaals

and (what is defined as) applications, and it depends upon the location of the software (public facing, web-based, AOC, and non-web-based).

On Thu, May 3, 2018, 8:55 PM Chaals Nevile <***@yandex.ru<mailto:***@yandex.ru>> wrote:
It is certainly possible to do this.

It is, as I understand it, the intention of the techniques documents to provide this information. One of the problems is getting people who have dealt with something not covered there already to actually provide the content so it can be added.

cheers

Chaals

On Thu, 03 May 2018 22:18:03 +0200, Emily Ogle <***@yahoo.com<mailto:***@yahoo.com>> wrote:

I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.

Emily Ogle

On May 3, 2018, at 10:32 AM, Russell, Jon (CTR) <***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>> wrote:
Can we start a database somehow contained is an area on this archive – like a wiki site – or somewhere else on the WAI site for:

508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)

Thanks,

Jon Russell
Software Tester
Section 508 Trusted Tester Certified 301122
DHS NPPD IP IICD Test & Evaluation (T&E)
1310 North Courthouse Road 04 – 306
Desk: 703-235-9306
Mobile: [phone]
***@associates.hq.dhs.gov<mailto:***@associates.hq.dhs.gov>

[c***@pubcom.com]

You can also hire software beta testers and advisors to help guide you during development, as well as testing interim and final versions before release.



There are fair number of them in the industry with deep knowledge of accessibility issues, as well as usability and UX.



--Bevi Chagnon

— — —

Bevi Chagnon, founder/CEO | <mailto:***@PubCom.com> ***@PubCom.com

— — —

PubCom: Technologists for Accessible Design + Publishing

consulting • training • development • design • sec. 508 services

Upcoming classes at www.PubCom.com/classes

— — —





From: Chaals Nevile <***@yandex.ru>
Sent: Thursday, May 3, 2018 8:37 PM
To: w3c-wai-***@w3.org
Subject: Re: 508 Software Tester Software Coding Advice for Software Developers



It is certainly possible to do this.



It is, as I understand it, the intention of the techniques documents to provide this information. One of the problems is getting people who have dealt with something not covered there already to actually provide the content so it can be added.



cheers



Chaals



On Thu, 03 May 2018 22:18:03 +0200, Emily Ogle <***@yahoo.com <mailto:***@yahoo.com> > wrote:



I know my organization has struggled with the challenges of developing accessible software, so I would find a resource quite helpful, though it wouldn’t necessarily need to be just Section 598, as EN 301 549 covers Section 508 and then some.



Emily Ogle


On May 3, 2018, at 10:32 AM, Russell, Jon (CTR) <***@associates.hq.dhs.gov <mailto:***@associates.hq.dhs.gov> > wrote:

Can we start a database somehow contained is an area on this archive – like a wiki site – or somewhere else on the WAI site for:



508 Software Tester Software Coding Advice for Software Developers – (as software testers find bugs/issues?)



Thanks,



Jon Russell

Software Tester

Section 508 Trusted Tester Certified 301122

DHS NPPD IP IICD Test & Evaluation (T&E)

1310 North Courthouse Road 04 – 306

Desk: 703-235-9306

Mobile: [phone]

***@associates.hq.dhs.gov <mailto:***@associates.hq.dhs.gov>