# data[].attributes.body
Please make sure the slides are accessible. Having a look at the accessibility checker, it says there are 1 hard to read contrast, 76 missing ALT texts, 1 missing table header, 78 missing slide titles and 10 reading order issues.

# data[].attributes.headline
Really helpful to understand work that is happening that will (hopefully) roll out to all of us soon. 

# data[].attributes.subject
Really helpful to understand work that is happening that will (hopefully) roll out to all of us soon. 

# data[].attributes.body
Could the presentation be recorded and shared? Maybe the show and tells? It's useful to review the slides afterwards, and without the talking the context is lost

# data[].attributes.body
I feel that the 1.5 hour setup for these meetings can feel too long at times. Its a large chunk of time during the day and often it feels like whilst there is useful information, it doesn't always actually impact my work and feels more like a backend piece of work that is important but isn't relevant to me.

# data[].attributes.headline
I think a list of contacts was mentioned. It would be good to hold something centrally so that I'm able to know who to contact in which department about GOV.UK. Could it be built into the user manager somehow? I could filter on leads?

# data[].attributes.subject
I think a list of contacts was mentioned. It would be good to hold something centrally so that I'm able to know who to contact in which department about GOV.UK. Could it be built into the user manager somehow? I could filter on leads?

# data[].attributes.body
Seeing forms in the wild was great

# data[].attributes.body
The show and tell on GOV.UK Forms was really helpful.

# data[].attributes.body
Felt a lot of information was condensed in the last session on publishing strategy and it would have been better to have more time to consider this.

# data[].attributes.body
I felt the second item was a bit pointless (sorry!), it's good to know the outcomes of an internal survey but could you perhaps just stick them on basecamp and direct us there. Then you could allow more time for slower pace and more detail on the important stuff like publisher changes and history mode.

# data[].attributes.body
Auditing content for history mode can actually be a bit more complex than the sides suggested (IMO) - would really benefit from having discussions on basecamp as per the other comment. Previous times it's been implemented the conversations were incredibly helpful

# data[].attributes.body
Would it be possible to have some area on Basecamp for discussion around history mode? I think it would be really useful to hear from other teams as I expect we'll have some of the same questions and concerns as we carry out the audit.

# data[].attributes.body
Front door/topic pages with improved functionality (we're getting a lot of requests to build small websites because the gov.uk function isn't engaging enough and doesn't bring together complex topic areas in a user friendly way - is there any scope to fix this in the future?

# data[].attributes.headline
Could there be a session to share knowledge about using GA4?

# data[].attributes.subject
Could there be a session to share knowledge about using GA4?

# data[].attributes.headline
Could we do a session to share knowledge on how AI can help content designers?

# data[].attributes.subject
Could we do a session to share knowledge on how AI can help content designers?

# data[].attributes.body
Thought-provoking talk on user needs and useful update on Gov Forms. Also nice to hear from the research team - it feels like they're engaging a lot with departments at the moment, which is much appreciated.

# data[].attributes.headline
Heard that other organisations are facing similar challenges - good to combine forces

# data[].attributes.subject
Heard that other organisations are facing similar challenges - good to combine forces

# data[].attributes.headline
Opportunity to hear what's going on at GDS

# data[].attributes.subject
Opportunity to hear what's going on at GDS

# data[].attributes.headline
Useful and concise talks about important topics

# data[].attributes.subject
Useful and concise talks about important topics

# data[].attributes.body
Couldn't attend as Zoom browser link didn't work.

# data[].attributes.headline
A Teams call so so that I could join using work IT

# data[].attributes.subject
A Teams call so so that I could join using work IT

# data[].attributes.headline
It was reassuring to hear/see others are having the same issues around PDFs and accessibility of content as sometimes it does feel like you're fighting this alone!

# data[].attributes.subject
It was reassuring to hear/see others are having the same issues around PDFs and accessibility of content as sometimes it does feel like you're fighting this alone!

# data[].attributes.headline
The mix up about whether the call was on google or zoom! ;-)

# data[].attributes.subject
The mix up about whether the call was on google or zoom! ;-)

# data[].attributes.body
Re post on account managers. We do (the Blue Team) and find them very helpful. However, it did take me about a year in the role to find out they existed. A better mechanism for checking who your account managers are might be useful.

# data[].attributes.headline
I have a question - do most departments have a direct contact within GDS (like an account manager)? We don't, but it would be really useful to have someone we can contact (other than through zendesk) to work through blockers, issues, large projects etc.

# data[].attributes.subject
I have a question - do most departments have a direct contact within GDS (like an account manager)? We don't, but it would be really useful to have someone we can contact (other than through zendesk) to work through blockers, issues, large projects etc.

# data[].attributes.body
This link doesn't work for me

# data[].attributes.body
Apologies, my attendence was interupted by an internal meeting that was unavoidable. Where I missed the Annual Reports section (and for those unable to attend at all), if not already planning to, could details of this be covered/shared in the post-meeting email - we have been following the thread on Basecamp with interest.
Thank you.