 Allâ! Yn olygr eich hyn yn ymwneud, fel Walthamhome, ymwneud yng Nghyrchol anodd, ac i ni'n ddod i ddim yn ddechrau, ac iddyn nhw'n ddoch am i ni'n ddigwiaeth allwch ei wneud i'n meddwl am ddweudio ar y wychau sydd wedi fath. Gallwn hi'n gweithio, dyma'r cyfrifio, hefyd maen nhw'n ddim yn ddod i ni. Felly wedi am y cyfrifio maen nhw'n ddigwiaeth ychydig yw eu ddweud, ac yn dweud o bwysig o'r ffordd meddwl i'r llyfr yn y Llyfr Gwyrdog yn ysgrifesio. There has been a wide range of changes that came in at the late of the year, which has tied in with the whole idea of the Llyfr Gwyrdog being a step change in professionalism and the highest standards for the Llyfr Gwyrdog. The place where as a gwnnw developer this was probably most obvious to me before I started looking into accessibility was the front end, The other is a newb to the newb to the newb to the newb. So we had to change all of our templates from PHP template to twig and it gave us a really good chance to review everything, to look at the markup that the platforms provide in and make sure it is accessible. Obviously the change in the template engine didn't bring accessibility benefits by itself because the rendrelation out is still in the HTML, but it is really good to do it. gyda'r rhendoliadau ond yn ymgyrch gael hwn o'r rhindol. Mae'n dweud o'r eich gwaith, yn llog o gwybod. Felly, beth mae'r gwaith yn cyfwyr cwntrach yn y ddechrau, mae'n fawr i'r gwasanaeth... Mae'r ddweud o'r ddweud o'r llog o fwy o gwneud o'r ddweud, mae'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud, mae adeilad yn ei ddweud o'r ddweud o'r ddweud o'r fath. SA, mae gen i'n ffordd ysgolwch nos i ddisewyddiant. Yna gweithio'r fynd oedd ar wladau fe ffordd. Mae gweithio eich gweithio i'r ffordd ac e'ch gweithio... ..au ychydig yn ymhellach, mae hi'n ymhellach a ffordd datblygiad ar hyn yn hyn? Dwi'n cael eu cyflu hwn ynglyn â those ynglynalu. Ymhellach eich gweithio i'r ffordd ar y pethau... ..i stry holdau a'r corwsfond yn y ddalol. There were quite a few of these orphan labels, and they were places where an input was being described somewhere on a page. And whoever wrote that had, with the best intentions, used the label element because they thought it was a label, which is right, but they were only halfway there because they hadn't used the for attribute to link the label to the actual input field. What that means is, when a page is being parsed by a screen reader or some otherimentos assist with technology felly mae eich cerddau o rhaid yn yma yn cael ei gynhyrch a'r tyd a'r cyflawnol. A dwi'n gweithio unrhyw o'r cyfeil iawn, ac mae'r cyflawnol yn cael ei gynhyrch i'r cyflawnol yn cael ei gynhyrch, ond mae'r penedigau'n meddwl i'ch gael. Yr ysgolwch cyfan efo'r hyn oherwydd fydd yn cael ei wneud yn cerddau, ac mae'r cerddau o'r cyfan yn cerddau. Yn y fath, mae eich gwasiwch yn cyffredig gyda'r cyfarwydd, Mae'r rydw i'r cyfnodd y cyfnodd hyffordd yma'n gwirio'r cyfnodd. Mae'r cyfnodd o'r cyfnodd yn drwgau'r gweithio ar y cwmdiannol cyllideb sydd gennym CSS. Cysylltu'r cyfnodd yn ymweld i'r cyfnodd a'r cyfnodd yn ei ddweud i'r cyfnodd yn y CSS. Felly mae'r cwmiannol cyfnodd yn ymweld i'r cyfnodd yn ymweld i'r cyfnodd, ac nid ydy'r cwmiannol cyfnodd yn eraill y cyfnodd i ddweud. Felly'r cyfnodd yn ymwybod yn gyfnodd yn cyfforddiol yn cyllideb cyfnodd yn CSS, ac yn gystrym gweld i gael ein bod oherwydd celaid wneud ymweld i ddweud. Mae'r cyfnodd mae'r cyfnodd yn ymweld i'r cyfnodd y byddwyd yn ei ddaluniau, ac mae yw gyfer y cyfnodd, mae'r cyfnodd yn ymweld i'r cyfnodd, I gyd dwi'n gynhyrchu bod hynny yn fwy o'r ddweud i ddweud o'r ffodol gweithio cymdeithasol neu'r ddweud. A gyd dwi'n gwybod, neu'r FHTML5 yn ei ddweud o'r bwysig ac mae'r fwysig ar y cyflodau yn mynd i'r ffordd fel y cyflodau mae'r cyflodau yn eu cyflodau. Fy hwnnw, mae'r Rhobos ystod yn ei ddweud o'r cyflodau ar y cyflodau. Y cwm ychydig i ddechrau drwpl 8 o'r ddyn nhw i ddweud, felly am yng nghydfyniad hon am gyfnodd drwpl 7, ydych yn ddechrau chymae'ch drwpl 10 ac mae'r bwysig o ddyn nhw i ddyddwch. Felly mae'r ddiff yn gweithio'r ddiff yn allan. Rydych yn ddiff, ac mae'r ddiff yn ddechrau yn ddiff. Mae'r ddiff yn ddiff yn ddiff yn ddiff, mae'r ddiff yn ddiff yn ddiff yn ddiff yn ddiff, Rydych yn ddiff yn ddiff yn ddiff. Today at Nav notation, we have a side for things like sidebars that have a complementary role to play rather than being actually online content we have a d Narrom Discover W HTML contractor we have Photos which is an obvious thing for design. These elements have implied meaning to your screen readers. I am going to show demo neck Pepper V vistwm t-keys and Voice Hamer which is the macOS, IOS screen reader. And I am going to show you a feature called WebRotor. Ac rhaid i argyrchu gwelwg yn gefnogi gwyllgofynion o'r gwir, a tynnod i weithio o'r hyn o'r gwir i'n ni gwych defineidol sy'n ei comisi gyd yn dda chi fel rhowch i chi'n ei ei wneud yn cael ei ddechrau i ei cyflogion o'r gweithioi, i mi ar y cyfnod podeidiol, oherwydd mae arno'r gweithio o ran university lays i gwyllgor. A arno'r gweithio wahanol o'r gweithio ar gyfer ario ac yn defnyddio cynwys, yng Nghymru yw'r sech sy'n gyda'r maen nhw'n gyda'r gwaith. Felly, yna'r cyfnod o'r cyfnod o'r bwysig, yn ymgwrdd, ond, yna'r cyfnod, yn ymgwrdd, yn ymgwrdd, yn ymgwrdd, yn ymgwrdd, yn ymgwrdd, yn ymgwrdd. Felly, mae'n cael ei bod yn cyfnod. Felly, mae'n cyfnod o'r bwysig. Mae'n cyfnod o'r bwysig o'r bwysig, mae'n cyfnod o'r bwysig. Mae angen i'ch gweld i'ch gweld. Rwy'n ddigon nhw, maen nhw'n fford anghoft a gyfnod o'r bwysig. Mae'w rhai'r bwysig o'r bwysig o'r bwysig, a fe wrth dechau yma ar yr Uned, yn ymgyrch â'r ffawr mewn. Mae'n bwysig o'r bwysig o'r bwysig. Felly, mae'n ddegon ei fod yn meddwl, maen nhw'n fwych, ond mae'n nhw'n rwy'n meddwl, i'w adebol i'r bwysig. y dyfodol yn oed y cywbeth? Ac byddwn ni yw'r cyfeiri sydd wedi'u havwneud a'u'r cyflwytaeth a'i gael ei'r cyflwytaeth ddarllen yn un digwydd. Mae'r cyflwytaeth yn unig, ac mae'r cyflwytaeth wedi gyfriedodd. Mae'r cyflwytaeth yn unig. Dwi'n ei ddweud â'r L5 yn ymgyrch ynerydd darllen. Mae'r cyflwytaeth yn unedd a'r cyflwytaeth yw pdwyshu'r cyflwytaeth yn'? sydd wedi'u gwahanol i gwblodi'ol gan hyry. to jump around on it. This is the title of an imaginatively named issue queue a ticket on Drupal.org, it's called Freedom for Field sets, along with the details, and what this is in relation to is an area where Drupal 7 was using the wrong type of HDMI element. We were using the field sets a lot to group things together but purely for cosmetic reasons, it was to create those expanding and contracting field sets sydd yn deallu i'r rhan o bob ymlaenewaeth fel gyda y ffordd. A mae'r cerdwyr hefyd o'r haff, a'r gweithio sydd wedi'i gynhyrchu'r gwrth gwrth gwrth gwrth gwrth gwrth. Felly, mae gennym yn y pizae, mae'r pwlethau yn y ffordd, mae'r llwyddon o'r cerdwyr o'r rhan o'r buttonau, mae'n gweithio'r ffordd o'r gwrth gwrth gwrth, ond yna'n gweithio'r gwrth gwrth gwrth gwrth gwrth, a phamau sy'n rhaid i'r cyffredinol yn ddifol o'i cyfrifio. Yn Dduple 8, rwy'n ddweud y Dduple 8, rydyn ni'n gwybod sy'n ddweud i'r rhan o'r fath o ddiff. Rydyn ni'n rhan o'n cyffredinol gyffredinol o'r ddiff o'r ddiff. Rydyn ni'n gwybod yna'r ddifol o'r L5, i ddiff o ffandysgau i'r newydd iechyd yn dweud. Dwi'n gwybod eich ffantau hynny, and I don't know how good the projector is. Details is teamed up with summary. What it does is it just creates a accordion effect for you. It's all native and handled by the browser. Rather than trying to reinvent the wheel and use something like a japer or UI for an accordion, you have to worry about the tab management of it, whether it has good focus styles or that sort of thing. This is all done by the browser. This is what it looks like unspiled. ..y'r ddaeth ymddangos iawn o blwyddyn, mae'r ddŵwn yn eu blynyddoedd yÕ yma yna. Felly mae'n rhaid eu 0nd yw bod sy'n gweld y dyfi ac y dyfi'r dyfodol. Felly'r ddŵwn yn ymderteidiaeth ymddych chi wedi wnaeth beth o'r cyllid sy'n fawr. Felly'r cyfleion efo'r cyflosio'r cwisio iawn, i gael gyda chi efo. Rwy'n arch ei wneud y byddwn 기iriaeth ac mae'n cofnir o ran o'r cyflosio efo'r cyflosio. ychydig i gael y ddweud y twyd i gael y cyflwyso a'r oedd gan yma ychydig i gael. A'r gael, mae hynny'n gwybod bryd, oherwydd, y nodi y cwyl ffyrdd yn cyflawn o'r ddweud. Felly, mae'n gydig i gael y gweithio oherwydd, yn ei ei ddweud o'r dweud o'r ddweud o'r ddweud. Oherwydd, mae'n gweithio o'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud o'r ddweud. Fi'r cwsiannau digon yw ffordd o Paedwch Cymru, a fydd yn cyfgoreddau'r cyffredin swyddi, pa ymdweithio'r gyffredin sy'n ymdweithio'r gael, oedd y gallwch ddim. Ac rwy'n arferwyr i wneud yn y ffrifau ac mae'n arferwyr o ffrifau'r gael, cyffredin ffyrwyr co epwrtiddedd, ac mae'r ffyrwyr obae ar rai cyflodyngus. Felly byddai fel ddweud yn dweud wrth gwrs bod hi'n ffordd o'i cefnogi, they're just there in Druplate for you. So, another area where Druplate's got stuff that was never in 7, or at least not in 7 without Comtrip, is WI area. So this stands for where accessibility initiatives accessible, rich internet applications. Doesn't really describe what it does, but at least it's relatively easy to pronounce. And the whole purpose of these attributes is to provide information to the accessibility API of a browser for things that wouldn't normally provide that information. So this is often used for custom UI elements. So if you have a QJ query UI also complete in Druplate, it uses a lot of WI area attributes to communicate to the assistant on what's going on. This is about to pop something out. This has got five options available to choose from. And these were around in the time of Druplate 7, but they wasn't a mature enough standard. And also they weren't valid at XHTML, so they couldn't really be used in Druplate 7, but with Druplate 6 into XHTML 5 it's fine to use them. Indeed, they're used quite widely. They're involved in landmarks, which is the stuff we looked at with the voiceover roster. The advantage of using the new XHTML 5 elements and the area attributes together is that sometimes users will have assistive technology that understands one or the other, or they'll have a browser that understands one or the other. So there's some duplication in giving a main element a role of main, but it's just a good idea for compatibility, really, and that's what we see in the core themes. We also get quite a lot of goodies from form API, and so invalid things are marked by area invalid, and that means that assistive technology would highlight those to the user as something that isn't acceptable and needs to be worked on, a required field to also highlight in a similar way, and views uses area sort to describe how tables of data are arranged, and also form API uses area described by so that if you are tapping through a form with a screen reader, not only do you have the label announced, but you also have the description announced as well, so it's clear what belongs to what, and there's hopefully a lot of context for each field and how well it's described. And this is another thing where you don't really have to think about it. If you're using form API in your custom work, it'll just do it for you, which is great. So Dreadblade had this idea of going off the island, and also the concept of things being proud of invented elsewhere, and that was the idea that we didn't have to do everything ourselves anymore, we didn't have to write a custom load or window plug-in, we didn't have to have our own custom auto-complete plug-in, and we bought in things from other projects, layout for open source projects. One of those was CK Editor, which now they were in core, so it's a WYSIWYG text editor. And it was actually brought into core with the sort of requirement that accessibility issues were resolved. So we said, we want to use your product, but there's some things we don't like about it, let's work together to fix that and then we can use it. And indeed, Dreadblade contributors worked with the CK Editor team, and also some developers from IBM to improve the accessibility of not only just CK Editor's interface, but the content it produces. So Dreadblade brought in a change where image fields are required to have an auto-tack by default. So if you're uploading an image, the assumption is that you want your CMS users to describe it in a way that's accessible. And for a while, images that were inserted for CK Editor didn't have the same requirement for an auto-tack, but then that was brought in for Dreadblade as well. And we've also allowed people to use head-ins with CK Editor, so head-ins are vital in structuring a page in a way that things like that voice over roads that can understand, whereas formerly the default text would be able to strip them out, but now it doesn't, which is good. Another really exciting thing is this ADDI, which is a numeronym, so it stands for accessibility because it begins with A, ends with Y, it's got 11 characters in between. So there's this ADDI checker plug-in, which is made by CK Source, who are the people behind CK Editor and the sort of commercial arm of that product. And they used to charge people for this plug-in, but last May on World Accessibility Wednesday, they actually made an open source, so now it's free for anyone to use. And what it is, is it's kind of like, if you think about a spell checker or that like clippy thing that Microsoft Office used to have, it's kind of a combination of those, but for content produced with CK Editor. So if your CMS users are going in and they're making images, not have auto-tacks and they're putting two links next to each other that links the same place but aren't merged, which would be annoying if you're having it read out because you'd have the same link read out twice. It will, when you click on that, it will scan through your content, it will find all the issues with that and it will not only point them out to you, but it will also suggest how to fix them or in some cases you can click a button and it will fix them for you. And there's actually an issue to have this in core. It's going to happen at some point and there's just some performance implications of bundling all this extra JavaScript. So that's cool. Views was also something that wasn't in D7 core but now it is and it's an area where there's been a lot of improvements and it requires substantial impact because views even is used for a lot of the admin listings. So if you make views more accessible, you make the output of it for site builders better but also you make the administration interface for Drupal itself more accessible. The main area where this was improved on was tables. So views can output tabular data and now it supports letting the users type in a caption in the summary. And the benefit of that is for a user user no system technology to navigate a table, it can be quite time consuming and challenging. So the summary and the caption let them know whether or not they want to engage with the table before they get stuck into using it. There's also some improvements around column headers which improves how the tables data is read out to people and that's also been expanded now to add row headers as well to create my really complicated tables. The next thing is something I've sort of touched on earlier is views used to use C tools for its modal. So it's our sort of custom Drupal centric thing. And now it's using jQuery UI which has the benefit of a lot more people working on it, a lot more people testing it. And jQuery UI is another thing which we bought into Core. So jQuery UI is used for our modal windows and it's used for our individual to complete so if you're tagging something or you're using an entry reference field. And it's a similar story as to a CK editor. We bought into Core but with the provision that it had to be super accessible and we worked to make it better. So the message behind this for developers really is to sort of think before you use like a custom Lightbox module or think before you bring in something from Bower or MPM because there might be something that does that already for you in jQuery UI which is easy to use in Core and it's now the encouragement to do. There's also this new modal and dialogue API which we don't really have time to go into. That's really cool. It's where I'm launching Drupal content in modal and that uses jQuery UI. But this is something that isn't probably invented elsewhere. This is something called Drupal and Alps which is really cool and we've got a demo of it coming up. It's basically almost like a text-to-speech API. So it's powered by ARIA attributes which we talked about earlier and it's powered by the ARIA Live attribute. What ARIA Live does is it says to the assistant technology this is a part of the page that's likely to change and if it changes I'd like you to announce that. So we can use that for things like a news feed which might have live news coming in or maybe like a live sports feed or a Twitter feed and it's basically used to announce changes which are initiated without a page reload and which would be obvious to a site user because something would pop up at the bottom or the top of the page but might not otherwise be obvious. And Drupal announce isn't hugely sophisticated. It's doing what you could do with just HTML in this ARIA Live region. But the benefit of it provides that it's consistent so call user's it, contract can use it and it also handles curing. So if you have two things sending a message very close to each other the messages will be combined and they'll be read out rather than one big cut-off as the other one comes in. So if you're not super familiar with using a screen reader it can be difficult to test but there's this devl develop adding module and what that does is it logs the announcements to the console so if I was to stick this JavaScript into my console to announce that there's like X items added to the feed that would be read out to me if I had my screen reader open but if I didn't I could see it as a JavaScript console message so it's useful for testing. I'm going to see an example now of Drupal announcements or at least something similar to it in jQuery UI being used to read out an also complete field. So this has got loads of devl generate content so it's going to read some stuff in Latin but what we're looking to do is find Amsterdam so we're going to start typing in this field and we should here eventually. Thank you. So we're having the text fields description read out to us and also some extra information from our other attributes so if we play that again we're going to start typing but to these initial ones but if we imagine we can't see Amsterdam's not there so we'll type some more. That's one result. That's what we want. And then we're on to next field. So that's how you can use a dynamic JavaScript base UI and by having it read out to you and then you can do or rather you can look at the contextual links module which has got loads of good examples of not only Drupal announcements but also the Drupal 8 tab management and this is another new thing in the Drupal 8 JavaScript API and what this is used for is restricting keyboard navigation through tab-in so if your users have a task where they only need to tap particular bits of the page and they don't want to go through every focus line so like every link, every form field you can actually pass a jQuery selector to this tab management API and then it will restrict the tab-in so an example of this is with the contextual links module so I've been able to develop Ali and it's highlighting all the areas where tab-in has been constrained to so what we're going to do is we're going to try and use the contextual links and you'll notice how it skips all the things that are in navigation so we can jump just between the contextual links without having to go through all the menu all of the sidebar stuff and so on so this is useful when you have when the user has chosen to do a particular thing so they might have chosen to launch a login form in a mode or window they might have expanded a slide-out menu and then you'd want to restrict the tab-in just to the menu and you'd want to only constrain it once the menu is closed and it's really easy to do you set up a tab-in context and then you call the tab-in manager with a jQuery you've got a jQuery selector and then later on you release it using the deactivate method so that's some JavaScript goodness we then have inline form errors and this has been going on forever so in 2009 someone raised an issue and they said when I fill in a form incorrectly the only way at a field level that the error has communicated to me is a red border so at the top of the form in the messages region you'd see the first name is a required field but when you actually got down to that field the only thing that's communicated to that in value state would be a red border which is no good if you're not a sighted user if you're a colourblind so there was a lot of discussion on that and then in 2012 the idea of showing inline form errors was proposed so this is showing the errors not on the top of the page but above the field and this issue ran all the way through to 2016 so we built up some momentum about inline form errors and it was going to be included in core and then it wasn't quite there yet so it was just too many varieties of forms that Dupal can produce and there were some issues where the messages wouldn't be displayed at all rather than above the form so it was included as an experimental module but with the demand or guidelines that we had to meet stability requirements earlier this year I wasn't included at all and those stability requirements were met there was a last minute effort to get it all sorted and it's a really good module because it meets current best practice so we built up form errors which we haven't had in due for at all and so we're now showing errors in context which is really good when you're partway through a massive form when you're fine, you have to keep scrolling up to see what's gone wrong so this is an example of errors previously so I haven't specified an orphan on the day and I haven't specified a title and this is a pretty basic page so it's kind of easy to see what's going on because on a smaller device or it was a much more complicated form the errors are showing at the top but apart from the red outline there's not much going on elsewhere on the form but if we install inline form errors we can see we still have a message at the top but it's now an improved message it's linking us to the fields which have the problems so orphan on and title are links there and then underneath title and underneath orphan on so it's much more easy to see at a glance where the problems are so that's stuff that Drupalake has given us and what's next there's a lot more work to be done accessibility is something that's not something you do and then you've done it, it's an ongoing process and the areas where there's work and excitement in Drupalake currently is for more JavaScript testing so now as well as the PHP tests on Drupalock we can run JavaScript tests and that's going to be really useful for finding the things that are quite laborious to test otherwise so in Drupalake we've had quite a lot of regressions around keyboard navigation so I was talking earlier about the markup cleaning and as part of that we took a lot of IDs out of our CSS IDs aren't a good thing because our CSS is super specific so I was moved to get rid of them and someone accidentally not only removed the IDs from the CSS but they thought hey now we're not using these for styling we can get rid of them in a markup if they're not being used by JavaScript but they were being used for some JavaScript around keyboard navigation so we were finding that you can open drop-down menus in some places with your keyboard but if we had JavaScript testing to simulate a user pressing tab, tab, tab, spacebar we'd be able to see whether or not the pages with interactive elements were working as they should be another area which is interesting is using third-party testing tools so it's one called Tenon which is Tenon.io and there's also an open source similar thing called Quail which was worked on by some people related to Drupal but there's kind of been a slowdown in its development recently which is why I haven't mentioned it in the slides another area is Windows High Contrast Mode so this is something that's really really popular by actual users but it doesn't really get a huge amount of attention from developers so that's something that we're looking to improve and do quite a moment and then the final thing which I think is really really cool and there's a video which we're going to look at next we can actually now in Safari at least choose whether or not to display animations to a user based on their system level preferences so Safari's launched basically a media query for people who are sensitive to motion so in your Mac OS settings as an accessibility tab you can choose to reduce the amount of animations that they're showing so on a computer this would mean that your doc menu doesn't sort of massively expand but it's also accessible to websites and this is a video made by a CSS Tricks contributor and this bit on the left is the right really crazy animation so if anyone's like feeling queasy or is motion sensitive probably women want to look at it but on the right hand side we've got our system preferences and we'll go into the accessibility settings and we'll see how the content on the web page can be transformed so there's your sort of animation and we open up our accessibility preferences and there's this reduced motion option and then the CSS even is picking that system preference up and it's showing sort of more simplified content so we could use that to sort of disable parallax scrolling effects to like prevent videos from playing in the background of content which would make the content a lot more accessible and we know that our content won't be covered earlier because we wanted to save the video till last so that's it, thank you very much everyone does anyone have any questions which I'll try and answer so there's a phenomenal resource called WebAIM which comes out at the University in States and this is a brilliant resource for everything to have accessibility basically and it's not too technical either so it's easy to sort of follow the wrong links and end up on like a spec or like really technical documentation but this isn't like that at all so WebAIM I'd recommend and also to sort of have a play around with a screen reader so like download ChromeVox or learn like the right keys to use for voiceover if you've got a Mac there's a bit of a learning curve to get inside with them there's lots of keyboard shortcuts which aren't immediately obvious once you've played around with them but it's really interesting to see how content's read out and how making some more changes affects that also another good thing is the Wave toolbar which is a more technical resource but it's shown in line with your content and it highlights how it's free do you know if you build a site in Google Aids and say for a content publisher a site for a university site how much accessibility do you have to do to get the select passing the requirements disability requirements to me all I agree with the name just as it's like back weight yeah so there's WPEG AAA and AAA AAA is seen as a standard to aspire to but something that would be very very difficult to reach whereas AA is more obtainable and the interesting thing with that question is if you use Drupal with minimal modifications it would be easy to meet the technical requirements but the issue would come from your content so quite a lot of accessibility issues are caused by people inputting content which is malformed so it doesn't have the right heading structure and they might try and change colour effects and Drupal actually did some stuff to change that so it got involved with something called WCAG which is yet another acronym but what that's about is not just making sure that your CMS is usable with assistive technology for visitors but also for content editors so if you're in a big organisation there'll be people in your organisation who might have a role in the website who might appreciate that sort of thing and it's also aiming to encourage people to produce accessible content which is similar to that thing with the plugin that I spoke about which looks for errors so I would definitely install that and try and also instill awareness of accessibility in your CMS editors and administrators so they are aware of what they shouldn't be doing and are comfortable with the ideas of that but in terms of technical accessibility it would depend on how much you extend Drupal so it depends on what custom work you do how adventurous your navigation systems get and that sort of thing but common pitfalls are headings images not having old tags and forms that aren't navigable so if you get the basics right you'll be in a good start and you'll have more time to look at the more sophisticated aspects Have you had the experience working with RMIB? No actually, I haven't but they have quite a lot of resources on the website so I should have mentioned earlier that there's no day in other charities to do a lot of work Previously it used to be a free service to not be charged for but you could actually as an institution take your site to the market and use the draws reader and the braille and various other things and do quite extensive tests That sounds good If you had a budget for it that would be a really good thing to do because it was quite hard to test accessibility and you'd need quite a wide amount of knowledge to get to do it in depth and just run it through the same tools that everyone else uses Anyone else? Hi So you mentioned standards like meeting aid on the way to work Have you found that actually in real life means that even if you hit the double A like practical use items one or those issues with keywords that actually practically translates to then being able to use the sites? Not always and actually we had an example of this on Friday I was at work and we've just like in the last few weeks of a project been asked to change the whole way the navigation worked and it's been like crazy and someone came back to us actually declined it they had something in-house to benefit and they said like with this navigation couldn't you put like ARIA has a pop-up here which is an ARIA activity that says click on this or expand something else and I was like yeah that's a good idea we definitely could have done that but when we'd been testing it with voice over ourselves and with people navigation it had been working fine so there's all those things that you can be doing but I guess if you write good HTML it should be usable in some way already Was it recommend people try to use voice over these because voice over needs to kind of like develop a different phase in a simple way should it be able to start maybe adopting voice over It depends on the project I suppose I mean ideally obviously the answer would be yes but that would be quite a time regime and it might be something that QA would do instead so it's something that I would encourage and it's an interesting thing to do I'm not sure if it's been forced on me Maybe you should Anyone else? All right then, thank you very much I'm not going around