Re: Admin accessibility

Hey Thibaud. Thanks for this, yes! On the team: I'm going to take the response here as approval and move that forward. Just haven't got to it yet. On the issues: All good, except I don't think we can actually remove as_p() and co. I think we'll have to go the Aria route. I haven't yet

Re: Admin accessibility

Hi all, I know setting up the team is still under way but in the meantime I wanted to bring your attention to a set of issues I recently reported about the accessibility of Django forms: - The as_table, as_ul, as_p output styles being inappropriate, https://code.djangoproject.com/ticket/32338

Re: Admin accessibility

Thanks all — I think we're there. All positives expressed. Do I need to ensure those who've not commented/voted do so? One question while we're here: * Do we have any specialist designers on board who could help serve on this team? * Related who can I ping ref the design on

Re: Admin accessibility

Taking this as a question posed under the DEP 10 voting process of whether or not to accept DEP 11: I vote +1. I think the basic idea is good; there are a couple things worth clarifying, mostly in terms of oversight, but that can be addressed in later edits. And by "oversight" I mean a clear

Re: Admin accessibility

I've made a few comments on the PR requesting clarification, but I see this as a big win. Comparing it to the "minimum criteria for a DEP"... It must be a clear and complete description of the proposed enhancement. > The only lack of clarity I see is around who's a member, and how renewing

Re: Admin accessibility

Hello all. Can I ask the Technical Board for Review and Resolution on DEP 11 please? https://github.com/django/deps/pull/69/ (Please let me know if I've done that wrong.) Kind regards, Carlton On

Re: Admin accessibility

Hi all. The DEP for creating an accessibility team is looking good. https://github.com/django/deps/pull/69 I'm going to ask for formal consideration shortly. If you have an interest/a moment, over the weekend say, to give it a glance before that, then any comments will be gratefully received

Re: Admin accessibility

I’d love to! But worth bearing in mind that I haven’t done any Django contributions before. I decided to end my talk with a call for feedback on your DEP – this feels like the ideal call to action to end on. On Monday, 14 September 2020 at 18:00:03 UTC+1 t...@carrick.eu wrote: > Carlton, I

Re: Admin accessibility

Carlton, I think that would be useful, thanks. Thibaud, shall I add you to the implementation team? It seems like you're doing more work on this than I am lately. I think we could still use one or perhaps two more people, but I think it's a good start. On Mon, 14 Sep 2020 at 16:44, Carlton

Re: Admin accessibility

Hi All. Thanks for this. I'd be happy to play *Shepherd *if you need someone to put their hand up. I think that means I need to nag about getting it done. So...  Who's going to be on the team to do the first review, and then subsequent work? Answer that and you have the Implementation Team.

Re: Admin accessibility

Hi all, Now that the DEP PR has been submitted I was wondering what the next steps would be. According to the documented DEP process I found, it’s at the "forming the team" stage? How do you go about

#31617 new New feature Improve overall admin accessibility.

Hello Team, I'm ready to work on this issue. Im a Full Stack dev by profession. I need to know what are necessary thing that i need to change and how do get the original code of that page. -- You received this message because you are subscribed to the Google Groups "Django

Re: Admin accessibility

 it’s wonderful to see this happening! Re-reading through the whole thing, as Tobias mentioned I also find it very easy to read, and makes a good case. On Tuesday, 14 July 2020 at 09:24:15 UTC+1 t...@carrick.eu wrote: > I've added a PR to the DEPs repo to hopefully get some eyes on it: >

Re: Admin accessibility

I've added a PR to the DEPs repo to hopefully get some eyes on it: https://github.com/django/deps/pull/69 Thibaud, I think whatever you have the time and motivation for sounds good, all of those things are useful. If you're not sure about all the admin features, I think that's pretty normal. One

Re: Admin accessibility

Update for the proof of concept CI tests from my side – thank you Tom for the feedback. Here are the latest additions to the test suite & reports, still living at https://thibaudcolas.github.io/django_admin_tests/, - Added as much as I know about in the admin, and now also outside of it a bit

Re: Admin accessibility

Nice writeup! I found it easy to read (I did not catch myself skipping paragraphs which is always a good sign). Contentwise, I would have no issue if this was accepted as is. Maybe I am forgetting about some important details though. I had just some ideas that might be good additions: - mention

Re: Admin accessibility

I've had some time to work on this, I've written up a draft... draft DEP today, and I'd like to request feedback. I've written it quite hastily over the last few hours with the expectation that it will need to be substantially rewritten. I've added it as a local PR on my fork of DEPS to keep the

Re: Admin accessibility

I've managed to have a quick look, it looks really promising. Having a total number of issues to compare against would be good to avoid regressions or introducing new issues. I do have one concern. To be viable, it needs to live in the django repo somewhere. And we'd need a full admin site to test

Re: Admin accessibility

Hi Tom, Great to hear – no rush if you’re busy with other things. Here’s a quick proof of concept, with 20 different pages/scenarios, tested with Axe, HTML Code Sniffer, and Lighthouse: https://github.com/thibaudcolas/django_admin_tests. I’m not a big fan of Lighthouse personally, and I

Re: Admin accessibility

A quick update first. I'm pretty busy with a combination of day job and personal projects, but I should have time to start writing the draft DEP in the next week or two. Thibaud, I think the absolute most important thing is a way to measure progress, even if - as others have mentioned - that

Re: Admin accessibility

Hey Tom, I wanted to check if there is anything we/I could do to help in the meantime? Whether that’s by starting to map or audit the Django admin, or setting up a sample CI pipeline with accessibility tests, or something else altogether. It’s a bit daunting to get started with this but I

Re: Admin accessibility

Some further thoughts... Mariusz, I don't think I agree that WCAG is massive. It can look a little large but I think that's mostly because each guideline is split into smaller pieces and it's quite wordy to avoid ambiguity. There are in 2.1 50 success criteria for AA, many of which can be checked

Re: Admin accessibility

Hi Tom, It’s exciting to see this getting started! To me a DEP would be highly beneficial, because there is a lot to this that goes beyond finding and fixing individual issues – it’s more about detailing the a process for parts of Django to stay accessible over time. Here are things I’d

Re: Admin accessibility

Hi, Thanks for the feedback. I had thought about a DEP when I was writing up the original post actually, I just wasn't sure what it should contain. Here are my thoughts, based on the feedback so far: - Defining a standard to target. - Forming an a11y team that covers the django admin and all

Re: Admin accessibility

Hi Tobias, I'm not a WCAG expert, and it's not clear to me what steps we would like to take. In the ticket we have only steps describes as *"very basics which should include"*, so I can imagine that's not all we need to do to be WCAG 2.1 compliant on AAA, AA or A level. As far as I'm

Re: Admin accessibility

Hi, felixxm proposed in https://code.djangoproject.com/ticket/31617 to add a DEP for this. The more I think about it, the less I agree. There is no DEP for security, usability, developer ergonomics or anything like that, so why should there be one for accessibility? Like with any of the other

Re: Admin accessibility

Hi all, I’m also interested in helping with this, although I’ve never been involved with Django development before. I’ve recently worked on a similar accessibility effort for Wagtail , a CMS built upon Django, which largely replaces the Django admin

Re: Admin accessibility

Hi everybody, I'm very interested in joining this conversation since I believe accessibility is an important issue and something often overlooked in applications such as the Django admin site. I come in representation of a software company called Talpor, located in Santiago de Chile, and we

Re: Admin accessibility

Hi there, I think it's a great initiative, even if as a person with physical disabilities, I've never been issues to use any kind of software. I would be happy to contribute but I'm not aware of any tool that can be integrated in any continuous integration system. Whenever I've been

Re: Admin accessibility

Hi all, I am legally blind. Accessibility discussions tend to largely revolve around contrast and screen readers (which I do not use) as it’s easy to measure for (albeit poorly without actually trying to use a screen reader yourself, which nobody tends to do). I am unsure if I have any valuable

Re: Admin accessibility

Hi Adam, > Which checker did you use? I had a brief check with a few. Firefox's devtools, Lighthouse, and WebAIM's WAVE browser extension. WAVE is quite nice in that it shows the problems directly on the page, but they all give more or less the same information. If Lighthouse can be integrated

Re: Admin accessibility

Hi Tom It's a laudable goal to make the admin accessible. Thank you for doing the research on currently laws and guidelines. I haven't audited the entire admin, but I have run a checker through some > pages. > Which checker did you use? I see Google's Lighthouse checks for many accessibility

Admin accessibility

Sorry, long post incoming. The admin currently has some accessibility issues. Not a huge amount, actually, but they should be fixed regardless. I hope I don't need to convince anyone here of the importance of accessibility, but I'll try to make the case as briefly as possible for the benefit of

Re: Admin accessibility tweaks

On Thu, Feb 25, 2010 at 12:29 AM, Chris Adams wrote: > We've been collecting various tweaks to the stock Django 1.1.1 which > have been requested by our 508 testers. I'd appreciate it if someone > could review these tickets: > > Add scope=col to changelist table headers: >

Admin accessibility tweaks

We've been collecting various tweaks to the stock Django 1.1.1 which have been requested by our 508 testers. I'd appreciate it if someone could review these tickets: Add scope=col to changelist table headers: http://code.djangoproject.com/ticket/12957 Add alt text to SelectFilter2's filter