https://padlet.com/benpoynton/o2gna13gd48ge9n3 en-us 2022-10-24 18:23:50 UTC 2023-04-13 19:56:43 UTC hello@padlet.com benpoynton https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553597542 E.g. I would always look to the policy before I embarked on any digital project and follow it perfectly.]]> 2023-04-13 18:52:36 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553597542 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647055 It is useful to say to a vendor, "look, here it is...we can't go against our policy" to push them]]> 2023-04-13 19:46:45 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647055 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647085 Would this be similar to IT security in terms of annual reports from divisions?

]]> 2023-04-13 19:46:48 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647085 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647223 I really like this idea and it would help to standardize how we create content, especially for internal platforms. It would be easier to train people on accessibility.]]> 2023-04-13 19:46:59 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647223 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647317 It would give me something to point to when encouraging instructors to do the work to make their courses accessible]]> 2023-04-13 19:47:07 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647317 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647437 From a UX Design perspective, a formal policy would help us vouch for adding dedicated development and testing time for accessible work within projects]]> 2023-04-13 19:47:17 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553647437 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648154 I think it's a good start as something we can point to, and then go from there if more is needed.]]> 2023-04-13 19:48:14 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648154 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648286 I think a formal policy would have to be kind of like job descriptions - say broadly what it has to do but not be too prescriptive about details.]]> 2023-04-13 19:48:22 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648286 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648412 Template reporting models. Can be adopted by divisions to assure their compliance. 

]]> 2023-04-13 19:48:33 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648412 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648440 2023-04-13 19:48:36 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648440 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648694 I think this approach is feasible and would be welcomed by the community. ]]> 2023-04-13 19:48:57 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553648694 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649139 2023-04-13 19:49:32 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649139 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649229 The EASI UX team uses a template whenever we're asked to look at the accessibility of an app/site, maybe that counts? It's basically just used to find issues and indicate which SC are broken so this may not apply here]]> 2023-04-13 19:49:40 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649229 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649857 In the past, web accessibility was the responsibility of divisions. Academic leaders did not always "own" this well.  Who will ultimately be responsible for compliance? Is this an "IT" thing, or non-IT divisional leaders responsibility to support and resource to met compliance targets?

]]> 2023-04-13 19:50:20 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553649857 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650051 2023-04-13 19:50:36 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650051 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650392 I mean...everyone has to follow it...]]> 2023-04-13 19:51:00 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650392 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650683 It would be definitely helpful to have something to refer to when creating accessible interfaces and help standardize how we create our tools and systems]]> 2023-04-13 19:51:23 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650683 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650814 I can see a bottle neck in having a single unit like EASI or AODA office responsible for reviews. We need a scalable option, with distributed responsibility. 

]]> 2023-04-13 19:51:33 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553650814 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553651404 2023-04-13 19:52:20 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553651404 douglasorme https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553652337 Terms like "policy" and "conformance" and "responsibility" while all useful and necessary lean heavily on the 'stick' side of the equation. A balance of success stories, testimonials, before-after revamps, easy-wins and the whole education piece may be as necessary for actual uptake of policy, no?

]]> 2023-04-13 19:53:28 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553652337 https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553654974 2023-04-13 19:56:43 UTC https://padlet.com/benpoynton/o2gna13gd48ge9n3/wish/2553654974